From: Greg KH <greg@kroah.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: lizf.kern@gmail.com, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] stable issues
Date: Sun, 4 May 2014 20:22:22 -0700 [thread overview]
Message-ID: <20140505032222.GA12867@kroah.com> (raw)
In-Reply-To: <CA+5PVA6sCLej9hhrRtaAw8hgrM7rw_R9-rWrH=VERdHY_fXGUg@mail.gmail.com>
On Sun, May 04, 2014 at 08:54:31AM -0400, Josh Boyer wrote:
> On Sun, May 4, 2014 at 7:19 AM, Li Zefan <lizefan@huawei.com> wrote:
> > I've been dealing with stable kernels. There are some issues that I noticed
> > and may be worth discussing.
> >
> > - Too many LTS kernels?
> >
> > 2.6.32 Willy Tarreau
> > 3.2 Ben Huchings
> > 3.4 Greg
> > 3.10 Greg
> > 3.12 Jiry Slaby
> >
> > Too many or not? Is it good or bad? One of the problem is the maintenance
> > burden. For example, DaveM has to prepare stable patches for 5 stable
> > kernels: 3.2, 3.4, 3.10, 3.12 and 3.14.
>
> To be fair, he doesn't have to. He chooses to, and it's great.
>
> > - Equip Greg with a sub-maintainer?
> >
> > I found 3.4.x lacked hundreds of fixes compared to 3.2.x. It's mainly
> > because Ben has been manually backporting patches which don't apply
> > cleanly, while Greg just doesn't have the time budget. Is it possible
> > that we find a sub-maintainer to do this work?
>
> I think you've already shown exactly how we can handle that. It just
> takes someone willing to do the work to dig in. Greg seemed very
> pleased with the patches for 3.4 being sent to him, and I know he's
> thanked me each time I send a report of what Fedora is carrying on top
> of a stable release. Do we need something more formal that what
> either of us have already done (or continue to do)?
I am really happy with people helping me out, and have asked for help in
the past.
The 3.4 patch work that has been going on is a great example of that,
and one that I am behind on in catching up with, due to travel, sorry.
If people want to come up with other ways of helping me, I'm all for it :)
thanks,
greg k-h
next prev parent reply other threads:[~2014-05-05 3:22 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 11:19 [Ksummit-discuss] [CORE TOPIC] stable issues Li Zefan
2014-05-04 12:04 ` Guenter Roeck
2014-05-04 12:54 ` Josh Boyer
2014-05-04 14:26 ` Guenter Roeck
2014-05-05 0:37 ` Josh Boyer
2014-05-05 3:09 ` Li Zefan
2014-05-05 3:47 ` Guenter Roeck
2014-05-05 11:31 ` Jason Cooper
2014-05-05 13:40 ` Guenter Roeck
2014-05-05 6:10 ` Michal Simek
2014-05-05 2:47 ` Li Zefan
2014-05-05 13:41 ` Theodore Ts'o
2014-05-05 15:23 ` Takashi Iwai
2014-05-05 15:39 ` Jan Kara
2014-05-05 16:02 ` Takashi Iwai
2014-05-05 16:07 ` Jason Cooper
2014-05-05 16:17 ` Takashi Iwai
2014-05-05 22:33 ` Greg KH
2014-05-06 3:20 ` Steven Rostedt
2014-05-06 4:04 ` Guenter Roeck
2014-05-06 10:49 ` Steven Rostedt
2014-05-05 3:22 ` Greg KH [this message]
2014-05-04 15:35 ` Ben Hutchings
2014-05-04 15:45 ` Guenter Roeck
2014-05-05 3:00 ` Li Zefan
2014-05-05 1:03 ` Olof Johansson
2014-05-07 2:49 ` Masami Hiramatsu
2014-05-07 2:58 ` Davidlohr Bueso
2014-05-07 8:27 ` Masami Hiramatsu
2014-05-07 8:39 ` Matt Fleming
2014-05-07 11:45 ` Masami Hiramatsu
2014-05-07 12:45 ` Daniel Vetter
2014-05-08 3:20 ` Masami Hiramatsu
2014-05-09 12:32 ` Daniel Vetter
2014-05-12 6:55 ` Masami Hiramatsu
2014-05-13 20:36 ` Steven Rostedt
2014-05-13 20:40 ` Davidlohr Bueso
2014-05-14 1:30 ` Masami Hiramatsu
2014-05-07 18:40 ` Davidlohr Bueso
2014-05-07 9:06 ` Dan Carpenter
2014-05-07 14:15 ` Jan Kara
2014-05-08 3:38 ` Li Zefan
2014-05-08 9:41 ` Jan Kara
2014-05-08 20:35 ` Andy Lutomirski
2014-05-09 4:11 ` Greg KH
2014-05-09 5:33 ` Masami Hiramatsu
2014-05-09 5:41 ` Greg KH
2014-05-07 3:05 ` Li Zefan
2014-05-07 3:31 ` Masami Hiramatsu
2014-05-07 7:20 ` Laurent Pinchart
2014-05-13 20:46 ` Steven Rostedt
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=20140505032222.GA12867@kroah.com \
--to=greg@kroah.com \
--cc=jwboyer@fedoraproject.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lizf.kern@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 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.