All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Paul Barker <pbarker@konsulko.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc
Date: Wed, 15 Jan 2020 13:46:46 -0500	[thread overview]
Message-ID: <CADkTA4OLsihtvEfMOsVjF1vqj-1=ogXywQij0dA6RHLo0CJTkQ@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4MSwdq_JjofhfyCJvQ=dY45G9tYhGtAp2Vv+7M-EB46Rw@mail.gmail.com>

On Wed, Jan 15, 2020 at 1:36 PM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> I already have an entire queue in development for this.
>
> So hold onto this series. I'll publish my branch later this week, or early next.

Actually, I'll see how it stacks on top of my changes and send a
unified branch to try out. That's probably the easiest way to get them
all working together.

Patches 2/3 look good, but I'd rather wait until we have the whole
series ready to go before Acking.

Cheers,

Bruce

>
> Bruce
>
> On Wed, Jan 15, 2020 at 1:08 PM Paul Barker <pbarker@konsulko.com> wrote:
> >
> > Patch 1 allows the kernel-yocto bbclass to be inherited directly in a recipe
> > without needing to use linux-yocto.inc. I can then use kconfig fragments in
> > my kernel recipe without pulling in the whole of linux-yocto.inc (which
> > includes some things I don't want like KERNEL_FEATURES changes and the
> > LINUX_VERSION_EXTENSION default).
> >
> > Patches 2 & 3 fix some minor issues I spotted while working on this.
> >
> > I've tested that linux-yocto can still be built for qemux86 after these
> > changes.
> >
> > Paul Barker (3):
> >   kernel-yocto: Move defaults and tasks from linux-yocto.inc into
> >     bbclass
> >   kernel-yocto: Drop setting of unused variables in do_kernel_metadata
> >   kernel-yocto: Only override CONFIG_LOCALVERSION if
> >     LINUX_VERSION_EXTENSION is set
> >
> >  meta/classes/kernel-yocto.bbclass         | 34 +++++++++++++++++------
> >  meta/recipes-kernel/linux/linux-yocto.inc | 21 --------------
> >  2 files changed, 25 insertions(+), 30 deletions(-)
> >
> > --
> > 2.20.1
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II



--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


  reply	other threads:[~2020-01-15 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 18:08 [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc Paul Barker
2020-01-15 18:08 ` [PATCH 1/3] kernel-yocto: Move defaults and tasks from linux-yocto.inc into bbclass Paul Barker
2020-01-15 18:08 ` [PATCH 2/3] kernel-yocto: Drop setting of unused variables in do_kernel_metadata Paul Barker
2020-01-15 18:08 ` [PATCH 3/3] kernel-yocto: Only override CONFIG_LOCALVERSION if LINUX_VERSION_EXTENSION is set Paul Barker
2020-01-15 18:36 ` [PATCH 0/3] Make kernel-yocto bbclass usable without linux-yocto.inc Bruce Ashfield
2020-01-15 18:46   ` Bruce Ashfield [this message]
2020-01-24 23:14     ` Bruce Ashfield

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='CADkTA4OLsihtvEfMOsVjF1vqj-1=ogXywQij0dA6RHLo0CJTkQ@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pbarker@konsulko.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.