From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] {linux, linux-headers}: add version 5.5
Date: Sun, 29 Mar 2020 18:52:50 +0200 [thread overview]
Message-ID: <20200329165250.GI22325@scaer> (raw)
In-Reply-To: <CAJiuCcdt69zFd6pQkTbJCfyWaYCpDC41ShN=Q71ZMKZdTuY9xQ@mail.gmail.com>
Cl?ment, All,
On 2020-03-29 17:34 +0200, Cl?ment P?ron spake thusly:
> On Sun, 29 Mar 2020 at 16:05, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2020-03-29 12:34 +0200, Cl?ment P?ron spake thusly:
> > > On Tue, 11 Feb 2020 at 23:41, Peter Korsgaard <peter@korsgaard.com> wrote:
> > > > Given that 5.5 is not a LTS kernel, I would prefer to hold back on this
> > > > patch until I release 2020.02-rc1 and create a next branch.
> > > The 2020.02 has been release and I'm interested to build against 5.5.
> > > Is this patch acceptable?
> > 2020.02 is a stable release (and even an LTS). Backports into such a
> > branch is limited to build fixes, and security fixes. No new feature is
> > backported there.
> Sorry I didn't mean backported to 2020.02, but merged into master or next.
Ah, sorry, I misread you.
Well, nothing prevents it from being merged, except for the roughly 500
other pending patches:
https://patchwork.ozlabs.org/project/buildroot/list/
I'll look into it now.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-03-29 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:21 [Buildroot] [PATCH] {linux, linux-headers}: add version 5.5 Jagan Teki
2020-02-11 22:41 ` Peter Korsgaard
2020-03-29 10:34 ` Clément Péron
2020-03-29 14:05 ` Yann E. MORIN
2020-03-29 15:34 ` Clément Péron
2020-03-29 16:52 ` Yann E. MORIN [this message]
2020-03-29 17:18 ` Yann E. MORIN
2020-03-29 20:50 ` Clément Péron
2020-04-02 15:41 ` Peter Korsgaard
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=20200329165250.GI22325@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.