All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich  Schuchardt <xypron.glpk@gmx.de>
To: Michal Suchanek <msuchanek@suse.de>, u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH] sandbox: Correctly define BITS_PER_LONG
Date: Sat, 22 Oct 2022 23:52:29 +0200	[thread overview]
Message-ID: <6F205FC0-7806-484A-AE74-DED469E504FB@gmx.de> (raw)
In-Reply-To: <20221022212201.24268-1-msuchanek@suse.de>



Am 22. Oktober 2022 23:22:01 MESZ schrieb Michal Suchanek <msuchanek@suse.de>:
>SANDBOX_BITS_PER_LONG is the number of bits in long on the sandbox
>platform.

Please, explain in the commit message what this patch is good for.

Aren't further patches needed to make use of it?

Best regards

Heinrich 

>
>Signed-off-by: Michal Suchanek <msuchanek@suse.de>
>---
>
> arch/sandbox/include/asm/types.h | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
>diff --git a/arch/sandbox/include/asm/types.h b/arch/sandbox/include/asm/types.h
>index c1a5d2af82..5f4b649ee3 100644
>--- a/arch/sandbox/include/asm/types.h
>+++ b/arch/sandbox/include/asm/types.h
>@@ -18,11 +18,7 @@ typedef unsigned short umode_t;
> /*
>  * Number of bits in a C 'long' on this architecture.
>  */
>-#ifdef	CONFIG_PHYS_64BIT
>-#define BITS_PER_LONG 64
>-#else	/* CONFIG_PHYS_64BIT */
>-#define BITS_PER_LONG 32
>-#endif	/* CONFIG_PHYS_64BIT */
>+#define BITS_PER_LONG CONFIG_SANDBOX_BITS_PER_LONG
> 
> #ifdef	CONFIG_PHYS_64BIT
> typedef unsigned long long dma_addr_t;

  reply	other threads:[~2022-10-22 21:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 20:28 [PATCH] tests: Build correct sandbox configuration on 32bit Michal Suchanek
2022-10-14  3:05 ` Heinrich Schuchardt
2022-10-14  8:43   ` Michal Suchánek
2022-10-15  5:00     ` Heinrich Schuchardt
2022-10-14 15:56 ` Simon Glass
2022-10-14 20:52   ` [PATCH v2] " Michal Suchanek
2022-10-15  4:54     ` Heinrich Schuchardt
2022-10-15  7:19       ` Michal Suchánek
2022-10-15 17:53     ` Simon Glass
2022-10-15 18:31       ` Heinrich Schuchardt
2022-10-15 18:39         ` Simon Glass
2022-10-15 19:05           ` Heinrich Schuchardt
2022-10-15 19:17             ` Michal Suchánek
2022-10-15 19:35               ` Heinrich Schuchardt
2022-10-15 19:24             ` Simon Glass
2022-10-15 19:29               ` Heinrich Schuchardt
2022-10-15 19:46                 ` Simon Glass
2022-10-15 20:27                   ` Heinrich Schuchardt
2022-10-17  7:28                     ` Michal Suchánek
2022-10-19 13:18                       ` Simon Glass
2022-10-22  1:05                       ` Simon Glass
2022-10-22 19:38                         ` Michal Suchánek
2022-10-22 21:22                           ` [PATCH] sandbox: Correctly define BITS_PER_LONG Michal Suchanek
2022-10-22 21:52                             ` Heinrich Schuchardt [this message]
2022-10-23  7:50                               ` Michal Suchánek
2022-10-23  7:56                                 ` Heinrich Schuchardt
2022-10-23 11:30                                   ` Michal Suchánek
2023-03-01 20:14                                   ` Simon Glass
2022-10-15  5:05   ` [PATCH] tests: Build correct sandbox configuration on 32bit Heinrich Schuchardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6F205FC0-7806-484A-AE74-DED469E504FB@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=msuchanek@suse.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.