From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
linux-block <linux-block@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Satya Tangirala <satyat@google.com>
Subject: Re: [PATCH 2/2] scsi: ufs: use devm_blk_ksm_init()
Date: Tue, 26 Jan 2021 22:01:47 -0500 [thread overview]
Message-ID: <yq1mtwvxf1s.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAPDyKFo_nsZuCX+nVBDTJ5QxZ18mQMx=MssJZtWTfJfFC=u+xw@mail.gmail.com> (Ulf Hansson's message of "Tue, 26 Jan 2021 10:57:59 +0100")
Ulf,
> I took the liberty of applying this one to my mmc tree along with
> patch1, as it looks trivial to me.
>
> Martin/James - if you have objections or want to ack it, please tell
> me.
That's fine. Just a heads-up that there has been a lot of churn in UFS
in this cycle so there may be some merge fuzz.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-01-27 4:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 8:21 [PATCH 0/2] Resource-managed blk_ksm_init() Eric Biggers
2021-01-21 8:21 ` [PATCH 1/2] block/keyslot-manager: introduce devm_blk_ksm_init() Eric Biggers
2021-01-25 20:14 ` Satya Tangirala
2021-01-25 20:25 ` Eric Biggers
2021-01-25 21:16 ` Jens Axboe
2021-01-26 9:57 ` Ulf Hansson
2021-01-21 8:21 ` [PATCH 2/2] scsi: ufs: use devm_blk_ksm_init() Eric Biggers
2021-01-25 20:18 ` Satya Tangirala
2021-01-26 9:57 ` Ulf Hansson
2021-01-27 3:01 ` Martin K. Petersen [this message]
2021-01-21 12:50 ` [PATCH 0/2] Resource-managed blk_ksm_init() Ulf Hansson
2021-01-25 21:14 ` Jens Axboe
2021-01-25 21:21 ` Eric Biggers
2021-01-25 21:23 ` Jens Axboe
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=yq1mtwvxf1s.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=ebiggers@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyat@google.com \
--cc=ulf.hansson@linaro.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 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).