All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] SCSI device blacklist handling improvements
Date: Wed, 06 Dec 2017 21:03:10 -0500	[thread overview]
Message-ID: <yq1k1xzxpk1.fsf@oracle.com> (raw)
In-Reply-To: <20171204183633.32139-1-bart.vanassche@wdc.com> (Bart Van Assche's message of "Mon, 4 Dec 2017 10:36:30 -0800")


Bart,

> These three patches is what I came up with after having reviewed
> recent changes in the code for handling blacklist flags
> handling. Please consider these patches for kernel v4.16.

I applied 1 and 3 to 4.16/scsi-queue. I am still not a fan of forcing
u32. That's a recipe for disaster when we add the next flag.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2017-12-07  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 18:36 [PATCH 0/3] SCSI device blacklist handling improvements Bart Van Assche
2017-12-04 18:36 ` [PATCH 1/3] scsi_get_device_flags_keyed(): Always return device flags Bart Van Assche
2017-12-04 18:36 ` [PATCH 2/3] Use blist_flags_t consistently Bart Van Assche
2017-12-04 18:36 ` [PATCH 3/3] Introduce scsi_devinfo_key enumeration type Bart Van Assche
2017-12-07  2:03 ` Martin K. Petersen [this message]
2017-12-07 17:34   ` [PATCH 0/3] SCSI device blacklist handling improvements Bart Van Assche
2017-12-08  1:10     ` 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=yq1k1xzxpk1.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=bart.vanassche@wdc.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@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 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.