From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v3 0/3] Rework handling of scsi_device.vpd_pg8[03]
Date: Mon, 28 Aug 2017 20:46:49 +0000 [thread overview]
Message-ID: <1503953208.2841.52.camel@wdc.com> (raw)
In-Reply-To: <20170828204446.29066-1-bart.vanassche@wdc.com>
On Mon, 2017-08-28 at 13:44 -0700, Bart Van Assche wrote:
> The conclusion of a recent discussion about the handling of SCSI device VPD
> [ ... ]
Please ignore this patch series too - same problem as last time.
Bart.
next prev parent reply other threads:[~2017-08-28 20:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 20:44 [PATCH v3 0/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 1/3] rcu: Introduce rcu_swap_protected() Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 2/3] Rework the code for caching Vital Product Data (VPD) Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 3/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 0/3] " Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 1/3] rcu: Introduce rcu_swap_protected() Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 2/3] Rework the code for caching Vital Product Data (VPD) Bart Van Assche
2017-08-28 20:44 ` [PATCH v3 3/3] Rework handling of scsi_device.vpd_pg8[03] Bart Van Assche
2017-08-28 20:46 ` Bart Van Assche [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 20:46 [PATCH v3 0/3] " Bart Van Assche
2017-08-28 20:45 Bart Van Assche
2017-08-28 20:45 ` Bart Van Assche
2017-08-28 20:47 ` Bart Van Assche
2017-08-28 20:41 Bart Van Assche
2017-08-28 20:41 ` Bart Van Assche
2017-08-28 20:43 ` Bart Van Assche
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=1503953208.2841.52.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.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.