From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Nicholas Piggin" <npiggin@gmail.com>,
"Bernhard Beschow" <shentey@gmail.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>, <qemu-devel@nongnu.org>,
<qemu-ppc@nongnu.org>
Cc: "Daniel Henrique Barboza" <danielhb413@gmail.com>, <clg@kaod.org>
Subject: Re: [PATCH v3] docs/system/ppc: Document running Linux on AmigaNG machines
Date: Wed, 13 Mar 2024 00:34:47 +1000 [thread overview]
Message-ID: <CZRUH5CRDRDU.3NS44E5KB0SSY@wheely> (raw)
In-Reply-To: <CZRPETJSO62V.5YV22F323JKC@wheely>
On Tue Mar 12, 2024 at 8:36 PM AEST, Nicholas Piggin wrote:
> On Tue Mar 12, 2024 at 7:28 PM AEST, Bernhard Beschow wrote:
> >
> >
> > Am 9. März 2024 11:34:56 UTC schrieb BALATON Zoltan <balaton@eik.bme.hu>:
> > >On Thu, 29 Feb 2024, BALATON Zoltan wrote:
> > >> On Wed, 21 Feb 2024, BALATON Zoltan wrote:
> > >>> Documentation on how to run Linux on the amigaone, pegasos2 and
> > >>> sam460ex machines is currently buried in the depths of the qemu-devel
> > >>> mailing list and in the source code. Let's collect the information in
> > >>> the QEMU handbook for a one stop solution.
> > >>
> > >> Ping? (Just so it's not missed from next pull.)
> > >
> > >Ping for freeze.
> >
> > Has this patch been tagged yet? It would really be a pity if it didn't make it into 9.0.
>
> Will send out a PR today and I'll include it.
>
> >
> > FWIW:
> >
> > Reviewed-by: Bernhard Beschow <shentey@gmail.com>
>
> Thanks, always helpful.
Oh you are Co-author. Sorry, took some time for light bulb
to turn on... In that case it needs your SOB to merge.
I will have to leave it out of the PR if I don't get that in
time, but we should be able to get a doc improvement past
the soft freeze. It's essentially a usability bug-fix.
Thanks,
Nick
>
> Thanks,
> Nick
>
> >
> > >
> > >> Regards,
> > >> BALATON Zoltan
> > >>
> > >>> Co-authored-by: Bernhard Beschow <shentey@gmail.com>
> > >>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> > >>> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> > >>> Tested-by: Bernhard Beschow <shentey@gmail.com>
[...]
next prev parent reply other threads:[~2024-03-12 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 23:22 [PATCH v3] docs/system/ppc: Document running Linux on AmigaNG machines BALATON Zoltan
2024-02-29 11:58 ` BALATON Zoltan
2024-03-09 11:34 ` BALATON Zoltan
2024-03-12 9:28 ` Bernhard Beschow
2024-03-12 10:36 ` Nicholas Piggin
2024-03-12 14:34 ` Nicholas Piggin [this message]
2024-03-12 15:50 ` BALATON Zoltan
2024-03-12 23:21 ` Bernhard Beschow
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=CZRUH5CRDRDU.3NS44E5KB0SSY@wheely \
--to=npiggin@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.com \
/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.