From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: hare@suse.de, jthumshirn@suse.de, hch@lst.de,
Mark Salyzyn <salyzyn@google.com>,
Robb Glasser <rglasser@google.com>,
Doug Gilbert <dgilbert@interlog.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: sg: Prevent potential double frees in sg driver
Date: Thu, 3 Aug 2017 12:51:05 -0700 [thread overview]
Message-ID: <20170803195105.GB26674@kroah.com> (raw)
In-Reply-To: <CAKwvOdmkCtmceK8prnZJn6QQ9oReN2EUMSukWLS=NmgF_GagiQ@mail.gmail.com>
On Thu, Aug 03, 2017 at 12:34:51PM -0700, Nick Desaulniers wrote:
> > Why no one on the to: line?
>
> I usually cc everyone from get_maintainer.pl. Should I be using
> --to= then explicitly for named folks, and --cc= for lists?
That's usually a good idea, many email clients throw away stuff if there
is nothing on the "To:" line.
> > And do you want this in the stable kernel trees?
>
> Looks like I can follow up on option #2 once this patch has
> been reviewed+merged by maintainers. I'll note to use
> option #1 next time, unless you suggest I send a v2? I can
> do so if this patch has a v2+.
If you have to resend it, then add it, otherwise please remember when it
hits Linus's tree to send the git commit id to stable@vger and the
developers there can handle it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-03 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 19:02 Nick Desaulniers
2017-08-03 19:23 ` Greg KH
2017-08-03 19:34 ` Nick Desaulniers
2017-08-03 19:51 ` Greg KH [this message]
2017-08-05 11:37 ` Christoph Hellwig
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=20170803195105.GB26674@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ndesaulniers@google.com \
--cc=rglasser@google.com \
--cc=salyzyn@google.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
all inboxes | Powered by JetHome®