From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Jens Rehsack <rehsack@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds
Date: Tue, 15 Sep 2020 12:45:16 +0100 [thread overview]
Message-ID: <d14f6deec304b5d5d7daddc1500dd32e21d00b0c.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4MFzRoKSV6+kBvYvsQ-BfFwt4BJuOj5bPpfQLYbJk_vmg@mail.gmail.com>
On Tue, 2020-09-15 at 07:33 -0400, Bruce Ashfield wrote:
> On Tue, Sep 15, 2020 at 1:44 AM Jens Rehsack <rehsack@gmail.com>
> wrote:
> >
> >
> > > Am 15.09.2020 um 00:34 schrieb Bruce Ashfield <
> > > bruce.ashfield@gmail.com>:
> > >
> > > From: Jens Rehsack <sno@netbsd.org>
> > >
> > > Backporting the 10 patches since the lttng 2.12.2 release. We'll
> > > drop
> > > them once .3 is released, but for now, we need the fixes to build
> >
> > Yet another question: there is a stable-2.12 branch ... wouldn't it
> > be reasonable to use this one as upstream source instead of the
> > tarball?
> >
>
> We used to do that .. yes. But then the lttng recipe was changed away
> from git to using the tgz.
>
> I complained at the time (I'm sure it is in the archives for all to
> see), since I'm constantly doing new kernels and have to do this sort
> of exercise.
>
> The devupstream bbclass allows me to keep moving on my new kernels
> when I need to pick up changes for -dev, and luckily -stable doesn't
> normally need this sort of thing.
>
> IIRC it was switched to tgz since things like AUH work better with the
> tarballs, but I can't be sure.
>
> But let's just say that I agree that this recipe is better as a branch
> based, git recipe and not a tgz based recipe. I just haven't waded
> into the discussion to switch it back :)
Perhaps we have a need for both?
Cheers,
Richard
next prev parent reply other threads:[~2020-09-15 11:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 22:34 [PATCH 0/6] linux-yocto: consolidated pull request Bruce Ashfield
2020-09-14 22:34 ` [PATCH 1/6] linux-yocto/5.8: update to v5.8.8 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 2/6] linux-yocto/5.4: update to v5.4.64 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 3/6] linux-yocto/config: configuration warning cleanup Bruce Ashfield
2020-09-14 22:34 ` [PATCH 4/6] linux-yocto/5.8: update to v5.8.9 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 5/6] linux-yocto/5.4: update to v5.4.65 Bruce Ashfield
2020-09-14 22:34 ` [PATCH 6/6] lttng-modules: backport patches from 2.12.x to fix 5.4.64+ and 5.8.9+ builds Bruce Ashfield
2020-09-14 22:35 ` Bruce Ashfield
2020-09-15 5:03 ` [OE-core] " Jens Rehsack
2020-09-15 11:37 ` Bruce Ashfield
2020-09-15 5:44 ` Jens Rehsack
2020-09-15 11:33 ` Bruce Ashfield
2020-09-15 11:45 ` Richard Purdie [this message]
2020-09-15 11:53 ` Bruce Ashfield
2020-09-25 16:43 ` Steve Sakoman
2020-09-25 16:52 ` Bruce Ashfield
2020-09-25 19:48 ` Steve Sakoman
2020-09-27 21:18 ` Bruce Ashfield
[not found] ` <1638C0AFDA43827E.8201@lists.openembedded.org>
2020-09-28 17:44 ` Bruce Ashfield
2020-09-28 22:35 ` Steve Sakoman
2020-09-28 22:53 ` Bruce Ashfield
[not found] ` <16391475BC3C80C8.17908@lists.openembedded.org>
2020-09-29 14:54 ` Bruce Ashfield
2020-09-29 17:23 ` Steve Sakoman
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=d14f6deec304b5d5d7daddc1500dd32e21d00b0c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rehsack@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