From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/3] kernel-devsrc: Add needed fixes for 6.1+ kernel build on target on RISCV
Date: Thu, 08 Feb 2024 23:14:29 +0000 [thread overview]
Message-ID: <8c69ebb28a118852852b6b4011d3fa31f1640ec0.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4PBvG6GS33KpYpJxeDJjHMLqZo3P6b-VGrR2f408oKGqQ@mail.gmail.com>
On Tue, 2024-02-06 at 18:26 -0500, Bruce Ashfield wrote:
> On Tue, Feb 6, 2024 at 1:49 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> > meta/recipes-kernel/linux/kernel-devsrc.bb | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
> > index 9c3c09e7144..07a20feb8ef 100644
> > --- a/meta/recipes-kernel/linux/kernel-devsrc.bb
> > +++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
> > @@ -224,10 +224,16 @@ do_install() {
> > if [ "${ARCH}" = "riscv" ]; then
> > cp -a --parents arch/riscv/kernel/vdso/*gettimeofday.* $kerneldir/build/
> > cp -a --parents arch/riscv/kernel/vdso/note.S $kerneldir/build/
> > + # v6.1+
> > + cp -a --parents arch/riscv/kernel/asm-offsets.c $kerneldir/build/
> > if [ -e arch/riscv/kernel/vdso/gen_vdso_offsets.sh ]; then
> > cp -a --parents arch/riscv/kernel/vdso/gen_vdso_offsets.sh $kerneldir/build/
> > fi
> > - cp -a --parents arch/riscv/kernel/vdso/* $kerneldir/build/ 2>/dev/null || :
> > + cp -a --parents arch/riscv/kernel/vdso/* $kerneldir/build/ 2>/dev/null || :
>
> I'm just off a flight and running on very little sleep, but I can't
> tell what changed in the line
> above here. Is it whitespace ?
>
> > + if [ -e arch/riscv/kernel/compat_vdso/gen_compat_vdso_offsets.sh ]; then
> > + cp -a --parents arch/riscv/kernel/compat_vdso/gen_compat_vdso_offsets.sh $kerneldir/build/
> > + fi
>
> I realize I have a mix of conditionals and ||: in the file, but we've
> been doing most of
> the new additions without conditionals. Would the
> gen_compat_vdso_offsets.sh copy
> work in that style ?
>
> i.e. cp -a --parents
> arch/riscv/kernel/compat_vdso/gen_compat_vdso_offsets.sh
> $kerneldir/build/2>/dev/null || :
I ended up heavily cleaning up the whitespace in this file and this
patch.
If anyone wants to make the conditionals more consistent I'm fine with
that too, I tend to prefer the if blocks but you can argue it both
ways, as ever...
Cheers,
Richard
prev parent reply other threads:[~2024-02-08 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 18:49 [PATCH 1/3] kernel-devsrc: Add needed fixes for 6.1+ kernel build on target on RISCV Khem Raj
2024-02-06 18:49 ` [PATCH 2/3] rust/cargo: Build fixes to rust for rv32 target Khem Raj
2024-02-15 10:57 ` [OE-core] " Alexander Kanavin
2024-02-06 18:49 ` [PATCH 3/3] buildcpio.py: Switch to using cpio-2.15 Khem Raj
2024-02-06 23:26 ` [OE-core] [PATCH 1/3] kernel-devsrc: Add needed fixes for 6.1+ kernel build on target on RISCV Bruce Ashfield
2024-02-06 23:36 ` Khem Raj
2024-02-08 23:14 ` Richard Purdie [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=8c69ebb28a118852852b6b4011d3fa31f1640ec0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox