From: Andrew Lunn <andrew@lunn.ch>
To: Mark Salyzyn <salyzyn@android.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: refcount_t + (resend to wider audience)
Date: Fri, 28 Jul 2017 19:41:17 +0200 [thread overview]
Message-ID: <20170728174117.GL2132@lunn.ch> (raw)
In-Reply-To: <adaee9d9-1d35-921c-36b3-e32e6c8ce9e3@android.com>
On Fri, Jul 28, 2017 at 10:15:23AM -0700, Mark Salyzyn wrote:
> (Resend to wider audience to comply with
> Documentation/networking/netdev-FAQ.txt)
>
> Please apply/backport the following upstream feature and followup
> grouped fixes patches to the stable trees (expect included in at least
> 3.10.y, 3.18.y, 4.4.y and 4.9.y):
.. _stable_kernel_rules:
Hi Mark
Everything you ever wanted to know about Linux -stable releases
===============================================================
Rules on what kind of patches are accepted, and which ones are not, into the
"-stable" tree:
- It must be obviously correct and tested.
- It cannot be bigger than 100 lines, with context.
The first patch you list is 342 lines. The second one is 634.
Please could you read the rules and then provide some justification
for ignoring many of the rules.
Andrew
next prev parent reply other threads:[~2017-07-28 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cc109bec-d4bb-8965-3169-fe36d85e6e19@android.com>
2017-07-28 17:15 ` refcount_t + (resend to wider audience) Mark Salyzyn
2017-07-28 17:41 ` Andrew Lunn [this message]
2017-07-28 18:07 ` Mark Salyzyn
2017-07-28 19:31 ` David Miller
2017-07-28 19:59 ` Mark Salyzyn
2017-07-28 21:23 ` Andrew Lunn
2017-07-28 19:29 ` 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=20170728174117.GL2132@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=salyzyn@android.com \
--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).