From: Simon Glass <sjg@chromium.org>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH] sandbox: Correctly define BITS_PER_LONG
Date: Wed, 1 Mar 2023 12:14:18 -0800 [thread overview]
Message-ID: <CAPnjgZ20H8us0mBMAQEsvA3EUf+p-tfGyzUMFDUcVdnkD547zQ@mail.gmail.com> (raw)
In-Reply-To: <20221023113044.GA28810@kitsune.suse.cz>
On Sun, Oct 23, 2022 at 09:56:29AM +0200, Heinrich Schuchardt wrote:
> On 10/23/22 09:50, Michal Suchánek wrote:
> > On Sat, Oct 22, 2022 at 11:52:29PM +0200, Heinrich Schuchardt wrote:
> > >
> > >
> > > 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.
> >
> > For setting BITS_PER_LONG correctly.
> >
> > > Aren't further patches needed to make use of it?
> >
> > 'make ue of it' would likely by running 32bit sandbox with 64bit
> > phys_addr_t, and that indeed won't be fixed by this patch alone.
> >
> > Nonetheless, since nobody noticed that this is broken so far I figured I
> > will send the patch anyway.
> >
> > Thanks
> >
> > Michal
> >
> > > 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(-)
> > > >
Applied to u-boot-dm, thanks!
next prev parent reply other threads:[~2023-03-01 20:15 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
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 [this message]
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=CAPnjgZ20H8us0mBMAQEsvA3EUf+p-tfGyzUMFDUcVdnkD547zQ@mail.gmail.com \
--to=sjg@chromium.org \
--cc=msuchanek@suse.de \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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.