All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeffy <jeffy.chen@rock-chips.com>
To: Hannes Reinecke <hare@suse.de>,
	"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 15:40:23 +0800	[thread overview]
Message-ID: <59F03FE7.30803@rock-chips.com> (raw)
In-Reply-To: <312e3d67-add5-17ae-1aa7-fd0a17cc5c40@suse.de>

Hi Hannes,

On 10/25/2017 03:22 PM, Hannes Reinecke wrote:
> 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 :-)
>
Ok, will do that :)

> Cheers,
>
> Hannes
>

  reply	other threads:[~2017-10-25  7:40 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
2017-10-25  7:40       ` jeffy [this message]
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=59F03FE7.30803@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=hare@suse.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=james.bottomley@hansenpartnership.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.