From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Prepare for upstreaming Pixel 6 and 7 UFS support
Date: Fri, 30 Dec 2022 16:24:16 -0500 [thread overview]
Message-ID: <yq1y1qo4mbu.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20221208234358.252031-1-bvanassche@acm.org> (Bart Van Assche's message of "Thu, 8 Dec 2022 15:43:55 -0800")
Bart,
> The patches in this series are a first step towards integrating
> support in the upstream kernel for the UFS controller in the Pixel 6
> and 7. Please consider these patches for the next merge window.
Applied to 6.3/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-12-30 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 23:43 [PATCH v5 0/3] Prepare for upstreaming Pixel 6 and 7 UFS support Bart Van Assche
2022-12-08 23:43 ` [PATCH v5 1/3] scsi: ufs: Reduce the clock scaling latency Bart Van Assche
2022-12-08 23:43 ` [PATCH v5 2/3] scsi: ufs: Pass the clock scaling timeout as an argument Bart Van Assche
2022-12-08 23:43 ` [PATCH v5 3/3] scsi: ufs: Allow UFS host drivers to override the sg entry size Bart Van Assche
2022-12-30 21:24 ` Martin K. Petersen [this message]
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=yq1y1qo4mbu.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox