From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
SCSI <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Avi Shchislowski <Avi.Shchislowski@wdc.com>,
Alex Lemberg <Alex.Lemberg@wdc.com>,
Evan Green <evgreen@chromium.org>
Subject: Re: [PATCH v4 3/3] scsi: ufs-bsg: Allow reading descriptors
Date: Tue, 19 Feb 2019 19:30:31 -0500 [thread overview]
Message-ID: <yq1pnrnjo7s.fsf@oracle.com> (raw)
In-Reply-To: <SN6PR04MB4925FBBBAC3356886A02F46FFC7C0@SN6PR04MB4925.namprd04.prod.outlook.com> (Avri Altman's message of "Tue, 19 Feb 2019 11:44:27 +0000")
Hi Avri,
> A kind reminder.
It's expired from patchwork so now is an excellent time to repost.
Generally speaking, resubmitting patches is superior to pinging. While I
personally dig through the archives to revisit older patches, I can
almost guarantee that no other potential reviewers will do the same. The
best way to get a patch back on people's radar is to repost it.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-02-20 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 7:07 [PATCH v4 0/3] scsi: ufs-bsg: Add read descriptor Avri Altman
2019-01-27 7:07 ` [PATCH v4 1/3] scsi: ufs-bsg: Change the calling convention for write descriptor Avri Altman
2019-01-27 7:07 ` [PATCH v4 2/3] scsi: ufs: Allow reading descriptor via raw upiu Avri Altman
2019-01-31 9:22 ` [EXT] " Bean Huo (beanhuo)
2019-01-27 7:07 ` [PATCH v4 3/3] scsi: ufs-bsg: Allow reading descriptors Avri Altman
2019-01-28 18:42 ` Evan Green
2019-02-05 12:07 ` Avri Altman
2019-02-07 14:15 ` Avri Altman
2019-02-07 14:41 ` Martin K. Petersen
2019-02-19 11:44 ` Avri Altman
2019-02-20 0:30 ` Martin K. Petersen [this message]
2019-01-31 10:27 ` [EXT] " Bean Huo (beanhuo)
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=yq1pnrnjo7s.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Alex.Lemberg@wdc.com \
--cc=Avi.Shchislowski@wdc.com \
--cc=Avri.Altman@wdc.com \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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.