From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bean Huo <huobean@gmail.com>
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com,
asutoshd@codeaurora.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
cang@codeaurora.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] two UFS changes
Date: Tue, 8 Dec 2020 18:17:55 -0800 (PST) [thread overview]
Message-ID: <yq15z5bu3hw.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20201207190137.6858-1-huobean@gmail.com> <(Bean> <Huo's> <message> <of> <"Mon> <> <7> <Dec> <2020> <20:01:35> <+0100")>
Bean,
> Bean Huo (2):
> scsi: ufs: Remove an unused macro definition POWER_DESC_MAX_SIZE
> scsi: ufs: Fix wrong print message in dev_err()
Applied to 5.11/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-12-09 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 19:48 linux-next: Signed-off-by missing for commit in the scsi-fixes tree Stephen Rothwell
[not found] ` <(Stephen>
[not found] ` <Rothwell's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed>
[not found] ` <7>
[not found] ` <Nov>
[not found] ` <2018>
[not found] ` <06:48:34>
[not found] ` <+1100")>
2018-11-07 1:52 ` Martin K. Petersen
[not found] ` <Dec>
[not found] ` <2020>
[not found] ` <20:01:35>
[not found] ` <+0100")>
2020-12-09 2:17 ` Martin K. Petersen [this message]
[not found] <CGME20201207190149epcas5p2d877f4e3f6d31548d97f9b486d243a05@epcas5p2.samsung.com>
2020-12-07 19:01 ` [PATCH 0/2] two UFS changes Bean Huo
[not found] ` <(Bean>
2020-12-07 19:01 ` [PATCH 1/2] scsi: ufs: Remove an unused macro definition POWER_DESC_MAX_SIZE Bean Huo
2020-12-08 7:52 ` Avri Altman
2020-12-07 19:01 ` [PATCH 2/2] scsi: ufs: Fix wrong print message in dev_err() Bean Huo
2020-12-08 7:53 ` Avri Altman
2020-12-08 2:57 ` [PATCH 0/2] two UFS changes Alim Akhtar
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=yq15z5bu3hw.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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
Powered by JetHome