From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Guo Ren <guoren@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-csky@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 4/5] tools/nolibc: add csky support
Date: Mon, 30 Sep 2024 08:04:20 +0200 [thread overview]
Message-ID: <20240930060420.GB5109@1wt.eu> (raw)
In-Reply-To: <2f4a244d-e88c-4378-8b1b-71204964dab6@t-8ch.de>
On Mon, Sep 30, 2024 at 07:23:39AM +0200, Thomas Weißschuh wrote:
> > > [0] gcc 13.2.0 and 14.2.0 from kernel.org crosstools
> > > [1] https://github.com/XUANTIE-RV/qemu/
> > > [2]
> >
> > I think you wanted to place a link or something above for [2].
>
> [2] was supposed to be inline patches for QEMU, I'll try to make that a
> bit clearer.
>
> > > diff --git a/target/csky/cpu-param.h b/target/csky/cpu-param.h
> > > index 80554cc0fc03..9181b602a26f 100644
> > > --- a/target/csky/cpu-param.h
> > > +++ b/target/csky/cpu-param.h
> > (...)
> > > diff --git a/target/csky/op_vdsp2.c b/target/csky/op_vdsp2.c
> > > index a9985a03be33..d953f5ea94fe 100644
> > > --- a/target/csky/op_vdsp2.c
> > > +++ b/target/csky/op_vdsp2.c
> >
> > Also, the first two patches look like fixes for the arch itself, they
> > should really go outside of the nolibc development tree, at least
> > because they might have to be backported to some stable branches,
> > or later fixed/reverted in case they wouldn't be optimal.
>
> As mentioned above, these are patches for qemu, not Linux.
> I don't know enough about QEMU or C-SKY to know if these are the
> generally correct fixes. But they seem to work well enough for nolibc.
Ah I understand now. The problem with external patches inlined like this
is that it's hard to split them apart from the rest of the patch. For
example just doing patch -p1 < patch.mbox will fail, trying to patch
non-existing files.
What I'm used to doing when quoting code/patches/etc in messages is to
indent them by 2 or more chars. That could be sufficient to explain what
needs to be fixed in the upstream project without being taken for a part
of the patchset, especially for such tiny patches. In this case the quoted
part could include only the strict minimum (i.e. no diff --git header etc).
Just a suggestion.
Cheers,
Willy
next prev parent reply other threads:[~2024-09-30 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 21:47 [PATCH 0/5] csky: add shutdown and nolibc support Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 1/5] drivers/virt: introduce csky_exit system poweroff driver Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 2/5] tools/nolibc: provide a fallback for lseek through llseek Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 3/5] selftests/nolibc: add support to use standalone kernels for tests Thomas Weißschuh
2024-09-29 21:47 ` [PATCH 4/5] tools/nolibc: add csky support Thomas Weißschuh
2024-09-30 3:49 ` Willy Tarreau
2024-09-30 5:23 ` Thomas Weißschuh
2024-09-30 6:04 ` Willy Tarreau [this message]
2024-09-29 21:47 ` [PATCH 5/5] selftests/nolibc: skip test for getppid() on csky Thomas Weißschuh
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=20240930060420.GB5109@1wt.eu \
--to=w@1wt.eu \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.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