From: Andrew Lunn <andrew@lunn.ch>
To: Mark Salyzyn <salyzyn@android.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: refcount_t + (resend to wider audience)
Date: Fri, 28 Jul 2017 23:23:49 +0200 [thread overview]
Message-ID: <20170728212349.GA11564@lunn.ch> (raw)
In-Reply-To: <0eba17bc-218e-c45c-5a49-9313126cd018@android.com>
> Please, guidance on where I can go from here.
Hi Mark
Real fixes will be accepted. So check if there are any refcount fixes
which are not in stable. If so, ask for the fix to be added to stable.
A fix should be independent of the infrastructure used to find there
is an issue.
Andrew
next prev parent reply other threads:[~2017-07-28 21:23 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
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 [this message]
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=20170728212349.GA11564@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).