From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Viswas G <Viswas.G@microsemi.com>
Cc: Jack Wang <xjtuwjp@gmail.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Vasanthalakshmi.Tharmarajan@microsemi.com
Subject: Re: [PATCH 6/6] pm80xx : corrected linkrate value.
Date: Tue, 29 Aug 2017 21:32:25 -0400 [thread overview]
Message-ID: <yq14lsp263a.fsf@oracle.com> (raw)
In-Reply-To: <CAD+HZHUmNh1phB5TqGV97Cj8C=q_WG=W3CBgvFenMGxLNmsFkw@mail.gmail.com> (Jack Wang's message of "Tue, 29 Aug 2017 13:08:49 +0200")
Viswas,
Please send a v2 with correct dates and Jack's review tags added to each
patch.
Thank you!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-08-30 1:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 6:06 [PATCH 0/6] pm80xx updates Viswas G
2015-01-30 6:06 ` [PATCH 1/6] pm80xx : redefine sas_identify_frame structure Viswas G
2017-08-29 11:19 ` Jack Wang
2017-08-30 15:41 ` Viswas G
2017-08-30 16:03 ` Jack Wang
2017-08-30 16:28 ` Viswas G
2015-01-30 6:06 ` [PATCH 2/6] pm80xx: ILA and inactive firmware version through sysfs Viswas G
2017-08-29 11:26 ` Jack Wang
2015-01-30 6:06 ` [PATCH 3/6] pm80xx : Different SAS addresses for phys Viswas G
2017-08-29 11:25 ` Jack Wang
2017-08-30 16:55 ` Viswas G
2017-09-01 8:52 ` Jack Wang
2015-01-30 6:06 ` [PATCH 4/6] pm80xx : Corrected SATA abort handling Viswas G
2017-08-29 11:46 ` Jack Wang
2017-08-30 15:48 ` Viswas G
2015-01-30 6:06 ` [PATCH 5/6] pm80xx : panic on ncq error cleaning up the read log Viswas G
2017-08-29 11:49 ` Jack Wang
2015-01-30 6:06 ` [PATCH 6/6] pm80xx : corrected linkrate value Viswas G
2017-08-29 11:08 ` Jack Wang
2017-08-30 1:32 ` Martin K. Petersen [this message]
2017-08-25 21:47 ` [PATCH 0/6] pm80xx updates Martin K. Petersen
2017-08-26 5:27 ` Viswas G
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=yq14lsp263a.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Vasanthalakshmi.Tharmarajan@microsemi.com \
--cc=Viswas.G@microsemi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=xjtuwjp@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