From: Hannes Reinecke <hare@suse.de>
To: jeffy <jeffy.chen@rock-chips.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Bart van Assche <bart.vanassche@sandisk.com>,
linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCHv6,2/5] scsi: Export blacklist flags to sysfs
Date: Wed, 25 Oct 2017 09:22:17 +0200 [thread overview]
Message-ID: <312e3d67-add5-17ae-1aa7-fd0a17cc5c40@suse.de> (raw)
In-Reply-To: <59EFED5A.5050209@rock-chips.com>
On 10/25/2017 03:48 AM, jeffy wrote:
> Hi guys,
>
> maybe we need to add the generated scsi_devinfo_tbl.c into
> drivers/scsi/.gitignore :)
>
Indeed, maybe.
So here's your chance to get a patch upstream :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-10-25 7:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:26 [PATCHv6 0/5] scsi: Fixup blacklist handling Hannes Reinecke
2017-10-02 14:26 ` [PATCHv6 1/5] scsi_debug: allow to specify inquiry vendor and model Hannes Reinecke
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 2/5] scsi: Export blacklist flags to sysfs Hannes Reinecke
2017-10-02 16:35 ` Bart Van Assche
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-25 1:48 ` [PATCHv6,2/5] " jeffy
2017-10-25 7:22 ` Hannes Reinecke [this message]
2017-10-25 7:40 ` jeffy
2017-10-02 14:26 ` [PATCHv6 3/5] scsi_devinfo: Reformat blacklist flags Hannes Reinecke
2017-10-13 10:08 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 4/5] scsi_devinfo: Whitespace fixes Hannes Reinecke
2017-10-13 10:09 ` Johannes Thumshirn
2017-10-02 14:26 ` [PATCHv6 5/5] scsi_devinfo: fixup string compare Hannes Reinecke
2017-10-13 10:09 ` Johannes Thumshirn
2017-10-13 10:06 ` [PATCHv6 0/5] scsi: Fixup blacklist handling Hannes Reinecke
2017-10-17 5:06 ` Martin K. Petersen
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=312e3d67-add5-17ae-1aa7-fd0a17cc5c40@suse.de \
--to=hare@suse.de \
--cc=bart.vanassche@sandisk.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).