From: Bart Van Assche <bvanassche@acm.org>
To: Alim Akhtar <alim.akhtar@samsung.com>,
"'Martin K . Petersen'" <martin.petersen@oracle.com>
Cc: 'Jaegeuk Kim' <jaegeuk@kernel.org>,
'Avri Altman' <avri.altman@wdc.com>,
'Adrian Hunter' <adrian.hunter@intel.com>,
linux-scsi@vger.kernel.org, 'Kiwoong Kim' <kwmad.kim@samsung.com>,
"'James E.J. Bottomley'" <jejb@linux.ibm.com>,
'Krzysztof Kozlowski' <krzysztof.kozlowski@linaro.org>,
'Chanho Park' <chanho61.park@samsung.com>,
'Bean Huo' <beanhuo@micron.com>
Subject: Re: [PATCH 2/3] scsi: ufs: Exynos: Fix the maximum segment size
Date: Thu, 12 Jan 2023 14:37:08 -0800 [thread overview]
Message-ID: <af53b716-9cbb-5048-e5a9-9026f44a41b8@acm.org> (raw)
In-Reply-To: <018d01d92584$f5d57c60$e1807520$@samsung.com>
On 1/10/23 22:21, Alim Akhtar wrote:
> For some reason, I didn't receive you patch-3/3 in my inbox.
That's unfortunate. That's probably because I use a shell script to
generate the Cc-list for UFS driver patches:
scripts/get_maintainer.pl --no-git --no-l --no-r --no-roles
--no-rolestats "${1:-&STDIN}"
Anyway, patch 3/3 is available here:
https://lore.kernel.org/linux-scsi/20230106215800.2249344-4-bvanassche@acm.org/
Bart.
next prev parent reply other threads:[~2023-01-12 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 21:57 [PATCH 0/3] Enable DMA clustering in the UFS driver Bart Van Assche
2023-01-06 21:57 ` [PATCH 1/3] scsi: ufs: Exynos: Fix DMA alignment for PAGE_SIZE != 4096 Bart Van Assche
2023-01-11 6:20 ` Alim Akhtar
2023-01-06 21:57 ` [PATCH 2/3] scsi: ufs: Exynos: Fix the maximum segment size Bart Van Assche
2023-01-11 6:21 ` Alim Akhtar
2023-01-12 22:37 ` Bart Van Assche [this message]
2023-01-06 21:58 ` [PATCH 3/3] scsi: ufs: Enable DMA clustering Bart Van Assche
2023-01-08 8:20 ` Avri Altman
2023-01-08 22:44 ` Bart Van Assche
2023-01-10 7:56 ` Adrian Hunter
2023-01-12 23:12 ` Bart Van Assche
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=af53b716-9cbb-5048-e5a9-9026f44a41b8@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=chanho61.park@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kwmad.kim@samsung.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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