From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: "julia.lawall@lip6.fr" <julia.lawall@lip6.fr>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: bug-introducing patches (or: -rc cycles suck)
Date: Mon, 30 Apr 2018 11:38:26 -0700 [thread overview]
Message-ID: <20180430183826.GA8287@kroah.com> (raw)
In-Reply-To: <20180430175829.GB1544@sasha-vm>
On Mon, Apr 30, 2018 at 05:58:30PM +0000, Sasha Levin wrote:
> Working on AUTOSEL, it became even more obvious to me how difficult it is for a patch to get a proper review. Maintainers found it difficult to keep up with the upstream work for their subsystem, and reviewing additional -stable patches put even more load on them which some suggested would be more than what they can handle.
>
<snip>
/me hands Sasha some extra '\n' characters
This is great info. Can you reformat your email to be sane and send
this to the ksummit discuss mailing list? I think the audience there
might be a bit more receptive than the noise that is lkml at times :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-30 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 17:58 bug-introducing patches (or: -rc cycles suck) Sasha Levin
2018-04-30 18:38 ` Greg KH [this message]
2018-04-30 19:09 ` Willy Tarreau
2018-05-01 16:19 ` Sasha Levin
2018-05-01 16:50 ` Willy Tarreau
2018-05-01 17:21 ` Sasha Levin
2018-04-30 19:12 ` Julia Lawall
2018-05-01 16:24 ` Sasha Levin
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=20180430183826.GA8287@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.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