stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Christoph Hellwig <hch@lst.de>, David Miller <davem@davemloft.net>
Cc: Bart.VanAssche@sandisk.com, torvalds@linux-foundation.org,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	stable@vger.kernel.org, ubraun@linux.vnet.ibm.com
Subject: Re: [PATCH] net/smc: mark as BROKEN due to remote memory exposure
Date: Tue, 16 May 2017 12:36:01 -0400	[thread overview]
Message-ID: <1494952561.3259.104.camel@redhat.com> (raw)
In-Reply-To: <20170516163041.GA5132@lst.de>

On Tue, 2017-05-16 at 18:30 +0200, Christoph Hellwig wrote:
> On Tue, May 16, 2017 at 12:29:23PM -0400, David Miller wrote:
> > 
> > I can't push back on people with silly coding style and small
> > semantic
> > issues forever.  And I think I made a serious effort to keep the
> > patches getting posted over and over again to make sure they got
> > more
> > exposure.
> 
> You can tell them to go to linux-rdma.  I'm sending people to the
> right
> mailing list all the time.

Indeed.  Every single time a patch comes into linux-rdma that touches
things in net/ or include/net, unless it is exceedingly minor, I check
the To:/Cc: lines on the email and if netdev@ isn't included, or in the
case of complex/tricky items, you aren't directly Cc:ed, then I
specifically tell them to include netdev@ and/or you.  I've even had
things like a 12 patch series that buried three netdev@ appropriate
patches at different points in the series and told the submitter to
move all of the netdev@ related patches to the front and submit them to
netdev@ so they can be reviewed as a group before I would move on to
the others.  It's just what you do.  I've always considered that part
of my job.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
   
Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

  parent reply	other threads:[~2017-05-16 16:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  7:26 [PATCH] net/smc: mark as BROKEN due to remote memory exposure Christoph Hellwig
2017-05-11 14:57 ` Bart Van Assche
2017-05-14  5:58   ` Christoph Hellwig
2017-05-14 15:51     ` David Miller
2017-05-14 19:08       ` Bart Van Assche
2017-05-15  0:44         ` David Miller
2017-05-15  1:58           ` Parav Pandit
2017-05-16 15:57           ` Doug Ledford
2017-05-16 16:29             ` David Miller
2017-05-16 16:30               ` Christoph Hellwig
2017-05-16 16:33                 ` David Miller
2017-05-16 16:35                   ` Christoph Hellwig
2017-05-16 16:36                 ` Doug Ledford [this message]
2017-05-16 16:41                   ` David Miller
2017-05-16 17:12                     ` Doug Ledford
2017-05-16 16:42               ` Doug Ledford
2017-05-16 16:49                 ` David Miller
2017-05-16 17:20                   ` Doug Ledford
2017-05-16 17:36                     ` David Miller
2017-05-16 18:03                       ` Doug Ledford
2017-05-16 18:52                         ` David Miller
2017-05-16 19:28                           ` Doug Ledford
2017-05-17 20:37                             ` Doug Ledford
2017-05-17 22:37                               ` Parav Pandit
2017-05-18  0:07                                 ` Doug Ledford
2017-05-18  4:22                                   ` Leon Romanovsky
2017-05-15  6:41       ` Sagi Grimberg
2017-05-15  7:18       ` Leon Romanovsky

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=1494952561.3259.104.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=Bart.VanAssche@sandisk.com \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ubraun@linux.vnet.ibm.com \
    /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).