From: Johannes Thumshirn <jthumshirn@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
stable@vger.kernel.org, Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: [PATCH] scsi: sg: fix SG_DXFER_FROM_DEV transfers
Date: Wed, 19 Jul 2017 08:48:38 +0200 [thread overview]
Message-ID: <20170719064838.GB4151@linux-x5ow.site> (raw)
In-Reply-To: <20170718161829.GA27190@kroah.com>
On Tue, Jul 18, 2017 at 06:18:29PM +0200, Greg KH wrote:
> On Tue, Jul 18, 2017 at 11:54:31AM -0400, Martin K. Petersen wrote:
> >
> > Greg,
> >
> > > On Tue, Jul 18, 2017 at 09:42:21AM +0200, Johannes Thumshirn wrote:
> > >> (commit 68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47 upstream)
> > >
> > > There is no such commit in Linus's tree :(
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/sg.c?id=68c59fcea1f2c6a54c62aa896cc623c1b5bc9b47
>
> {sigh} I hadn't updated my local tree.
>
> As this isn't in a -rc kernel yet, is it ok for me to wait until it
> shows up in one before adding it to a stable tree?
>
> And why wasn't it marked with a "cc: stable" in it so this would all
> happen automatically?
Because I forgot it. I'm sorry.
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
prev parent reply other threads:[~2017-07-19 6:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 7:42 [PATCH] scsi: sg: fix SG_DXFER_FROM_DEV transfers Johannes Thumshirn
2017-07-18 7:50 ` Greg Kroah-Hartman
2017-07-18 7:52 ` Johannes Thumshirn
2017-07-18 15:45 ` Greg Kroah-Hartman
2017-07-18 15:54 ` Martin K. Petersen
2017-07-18 16:18 ` Greg Kroah-Hartman
2017-07-19 6:48 ` Johannes Thumshirn [this message]
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=20170719064838.GB4151@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=dgilbert@interlog.com \
--cc=gregkh@linuxfoundation.org \
--cc=martin.petersen@oracle.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).