From: Nithin Nayak Sujir <nsujir@broadcom.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <david.vrabel@citrix.com>,
<stable@vger.kernel.org>, <mchan@broadcom.com>
Subject: Re: [PATCH net] tg3: Fix deadlock in tg3_change_mtu()
Date: Thu, 6 Feb 2014 17:08:41 -0800 [thread overview]
Message-ID: <52F43219.8010809@broadcom.com> (raw)
In-Reply-To: <20140206.165448.1676259324527494823.davem@davemloft.net>
On 02/06/2014 04:54 PM, David Miller wrote:
>
> Networking patches should never be CC:'d to -stable. And you should
> never add the:
>
> Cc: <stable@vger.kernel.org>
>
> tag to networking commit messages.
>
> Instead, after the "---" delimiter, you should kindly request that
> I queue up that patch for stable, and why. I handle networking
> stable submissions on my own.
>
I apologize. For some reason, I was under the impression that the rule applied
to core networking and not driver-only changes. Will keep this in mind.
How should I proceed with this? Should I resubmit?
Also, I'm a little confused as to why my previous submissions to net with stable
Cc'd were ok. E.g. commit 375679104ab3ccfd18dcbd7ba503734fb9a2c63a - "tg3:
Expand 4g_overflow_test workaround to skb fragments of any size.". Did it slip
by because I didn't have the < >?
Thanks,
Nithin.
next prev parent reply other threads:[~2014-02-07 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 22:13 [PATCH net] tg3: Fix deadlock in tg3_change_mtu() Nithin Nayak Sujir
2014-02-07 0:54 ` David Miller
2014-02-07 1:08 ` Nithin Nayak Sujir [this message]
2014-02-07 1:10 ` David Miller
2014-02-07 4:06 ` David Miller
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=52F43219.8010809@broadcom.com \
--to=nsujir@broadcom.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=mchan@broadcom.com \
--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).