From: Sasha Levin <sasha.levin@oracle.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"gordan@bobich.net" <gordan@bobich.net>
Subject: Re: [PATCH v3.18] iwlwifi: pcie: support loading FW with extended mem range
Date: Thu, 10 Mar 2016 14:34:33 -0500 [thread overview]
Message-ID: <56E1CC49.5060806@oracle.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32EA68D3B@hasmsx107.ger.corp.intel.com>
On 03/10/2016 02:18 PM, Grumbach, Emmanuel wrote:
>> > Sorry about that, my scripts skipped it because it didn't have a cc: stable@ tag. Fixed that and added it to the queue.
>> >
> There are a few maintainers that don't want people to cc: stable@ in
> their commit message but send patches to stable manually when these
> commits hit Linus's tree. I doubt they send them to stable after having
> add cc: stable@ to the commit message. So you may have missed quite a
> few patches :)
Hm, you're right. Not too many missed, but still.
My scripts used to ignore mails that didn't have "cc: stable@" and were not
addressed directly to me. I handled the exception which is David Miller by
just doing it manually, but I guess that it isn't the only exception.
Thanks,
Sasha
prev parent reply other threads:[~2016-03-10 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 20:51 [PATCH v3.18] iwlwifi: pcie: support loading FW with extended mem range Emmanuel Grumbach
2016-02-07 21:00 ` Greg KH
2016-02-07 21:02 ` Grumbach, Emmanuel
2016-02-07 21:19 ` Greg KH
2016-03-10 10:46 ` Grumbach, Emmanuel
2016-03-10 16:30 ` Greg KH
2016-03-10 17:02 ` Grumbach, Emmanuel
2016-03-10 18:51 ` Sasha Levin
2016-03-10 19:18 ` Grumbach, Emmanuel
2016-03-10 19:34 ` Sasha Levin [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=56E1CC49.5060806@oracle.com \
--to=sasha.levin@oracle.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gordan@bobich.net \
--cc=gregkh@linuxfoundation.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 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.