From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Hannes Reinecke <hare@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
SCSI ML <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: devinfo: fix format of the device list
Date: Wed, 17 Jan 2018 01:37:58 -0500 [thread overview]
Message-ID: <yq1wp0hrnw9.fsf@oracle.com> (raw)
In-Reply-To: <20180115164723.1943-1-xose.vazquez@gmail.com> (Xose Vazquez Perez's message of "Mon, 15 Jan 2018 17:47:23 +0100")
Xose,
> Replace "" with NULL for product revision level, and
> merge TEXEL duplicate entries.
Applied to 4.16/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-01-17 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:47 [PATCH] scsi: devinfo: fix format of the device list Xose Vazquez Perez
2018-01-17 6:37 ` Martin K. Petersen [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=yq1wp0hrnw9.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=xose.vazquez@gmail.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).