From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Champion Chen <champion_chen@realsil.com.cn>,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] bluetooth: btusb: Fix issue with suspend
Date: Sat, 6 Sep 2014 12:19:41 -0700 [thread overview]
Message-ID: <20140906191941.GA1125@kroah.com> (raw)
In-Reply-To: <9F1659DE-61C2-4CA9-8696-16F120273154@holtmann.org>
On Sat, Sep 06, 2014 at 12:12:44PM -0700, Marcel Holtmann wrote:
> Hi Larry,
>
> >> one other thing. Please let maintainers decide when a patch is
> >> useful for stable and when not. Patches need to go upstream first
> >> anyway. People spamming stable@vger.kernel.org with patches that
> >> are not reviewed yet is pretty much a waste of time.
> >
> > Sorry. In the wireless tree, the patch author suggests that the
> > patch is suitable for stable. If the maintainer disagrees, he strips
> > the Cc to stable. It seems that you do it the other way. In either
> > case, I do not think the stable patches are picked up by the
> > maintainers of stable versions until the patch hits mainline.
>
> I have no idea what the stable@vger.kernel.org guys do with patches
> that are not yet upstream.
I ignore them :)
> However it is a waste of their time sending stuff to their mailing
> list that has not even seen a maintainer review. You can just mention
> it in the comment section that this might qualify for stable.
It doesn't bother me at all for the cc:, they are easy to filter away,
and it keeps me informed as to where patches will be coming from in the
future, and helps to track down things that get dropped.
thanks,
greg k-h
prev parent reply other threads:[~2014-09-06 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 15:16 [PATCH] bluetooth: btusb: Fix issue with suspend Larry Finger
2014-09-06 17:02 ` Marcel Holtmann
2014-09-06 17:16 ` Larry Finger
[not found] ` <540B4159.9000003-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2014-09-06 17:35 ` Marcel Holtmann
[not found] ` <D5B40282-A085-4B47-8F7B-27480CAB6B19-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2014-09-06 19:05 ` Larry Finger
2014-09-06 19:12 ` Marcel Holtmann
2014-09-06 19:19 ` Greg KH [this message]
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=20140906191941.GA1125@kroah.com \
--to=greg@kroah.com \
--cc=Larry.Finger@lwfinger.net \
--cc=champion_chen@realsil.com.cn \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).