From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Don Brace <don.brace@microsemi.com>
Cc: joseph.szczypek@hpe.com, gerry.morong@microsemi.com,
john.hall@microsemi.com, jejb@linux.vnet.ibm.com,
Kevin.Barnett@microsemi.com, Mahesh.Rajashekhara@microsemi.com,
bader.alisaleh@microsemi.com, hch@infradead.org,
scott.teel@microsemi.com, Viswas.G@microsemi.com,
Justin.Lindley@microsemi.com, scott.benesh@microsemi.com,
POSWALD@suse.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] smartpqi updates
Date: Mon, 02 Oct 2017 22:26:53 -0400 [thread overview]
Message-ID: <yq1wp4d0xw2.fsf@oracle.com> (raw)
In-Reply-To: <150654770573.11494.168365142464423047.stgit@brunhilda> (Don Brace's message of "Wed, 27 Sep 2017 16:29:53 -0500")
Don,
> These patches are based on Linus's tree
>
> The changes are:
> - update list of controllers
> - cleanup warning message
> - change driver version to 1.1.2-126
Applied to 4.15/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-10-03 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 21:29 [PATCH 0/3] smartpqi updates Don Brace
2017-09-27 21:29 ` [PATCH 1/3] smartpqi: update controller ids Don Brace
2017-09-29 12:08 ` Tomas Henzl
2017-09-27 21:30 ` [PATCH 2/3] smartpqi: cleanup raid map warning message Don Brace
2017-09-29 12:08 ` Tomas Henzl
2017-09-27 21:30 ` [PATCH 3/3] smartpqi: update driver version to 1.1.2-126 Don Brace
2017-09-29 12:08 ` Tomas Henzl
2017-10-03 2:26 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-11 20:24 [PATCH 0/3] smartpqi updates Don Brace
2020-11-17 4:03 ` Martin K. Petersen
2020-11-20 3:29 ` Martin K. Petersen
2023-12-19 19:36 Don Brace
2024-01-04 4:11 ` 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=yq1wp4d0xw2.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Justin.Lindley@microsemi.com \
--cc=Kevin.Barnett@microsemi.com \
--cc=Mahesh.Rajashekhara@microsemi.com \
--cc=POSWALD@suse.com \
--cc=Viswas.G@microsemi.com \
--cc=bader.alisaleh@microsemi.com \
--cc=don.brace@microsemi.com \
--cc=gerry.morong@microsemi.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.hall@microsemi.com \
--cc=joseph.szczypek@hpe.com \
--cc=linux-scsi@vger.kernel.org \
--cc=scott.benesh@microsemi.com \
--cc=scott.teel@microsemi.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.