From: "Jens Rehsack" <rehsack@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: richard.purdie@linuxfoundation.org,
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 07:44:50 +0200 [thread overview]
Message-ID: <486E178E-DCB8-4B23-B199-63231267196E@gmail.com> (raw)
In-Reply-To: <ced4f4ad5252bcc989f40b54341c0d7a5835bfce.1600122415.git.bruce.ashfield@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
> 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?
> against the latest 5.4, 5.8 and 5.9 kernels.
>
> We also bump the devupstream SRCREV to pickup the same changes.
> -=-=-=-=-=-=-=-=-=-=-=-
--
Jens Rehsack - rehsack@gmail.com
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2020-09-15 5:44 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 [this message]
2020-09-15 11:33 ` Bruce Ashfield
2020-09-15 11:45 ` Richard Purdie
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=486E178E-DCB8-4B23-B199-63231267196E@gmail.com \
--to=rehsack@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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