From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space
Date: Mon, 6 Mar 2023 13:56:58 +0100 [thread overview]
Message-ID: <CAMuHMdV+q28hy6qLZwaQLO4dSSZeRfDzDSXfHrJyaSVxq=p1Ew@mail.gmail.com> (raw)
In-Reply-To: <CACz-3rjsBjum7T+dt8MGuwThwV98NnKuB-DE-Z3=VYa=nSd6-A@mail.gmail.com>
On Thu, Feb 23, 2023 at 3:29 PM Kars de Jong <jongk@linux-m68k.org> wrote:
> Op do 23 feb. 2023 om 12:26 schreef Kars de Jong <jongk@linux-m68k.org>:
> > The calculation of end addresses of memory chunks overflowed to 0 when
> > a memory chunk is located at the end of 32-bit address space.
> > This is the case for the HP300 architecture.
> >
> > Signed-off-by: Kars de Jong <jongk@linux-m68k.org>a
>
> Whoops, looks like I botched the "Signed-off-by" in the commit,
> thinking I was in vi when it was nano.
> Please remove the extra "a" at the end when you commit it :-)
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
i.e. will queue as a fix in the m68k for-v6.3 branch,
with the above fixed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2023-03-06 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 11:23 [PATCH] m68k: fix for systems with memory at end of 32-bit address space Kars de Jong
2023-02-23 12:39 ` Geert Uytterhoeven
2023-02-23 14:05 ` Kars de Jong
2023-02-24 10:40 ` Kars de Jong
2023-02-24 11:01 ` Geert Uytterhoeven
2023-02-24 18:57 ` Michael Schmitz
2023-02-23 14:29 ` Kars de Jong
2023-03-06 12:56 ` Geert Uytterhoeven [this message]
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='CAMuHMdV+q28hy6qLZwaQLO4dSSZeRfDzDSXfHrJyaSVxq=p1Ew@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).