From: Arthur Simchaev <Arthur.Simchaev@wdc.com>
To: "martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"beanhuo@micron.com" <beanhuo@micron.com>,
Avi Shchislowski <Avi.Shchislowski@wdc.com>,
Daniil Lunev <dlunev@chromium.org>
Subject: RE: [PATCH] scsi: ufs-bsg: Remove ufs_bsg_get_query_desc_size function
Date: Sun, 11 Sep 2022 10:35:04 +0000 [thread overview]
Message-ID: <BY5PR04MB6327C911666B7A5AE0E92A96ED459@BY5PR04MB6327.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CAONX=-cXDcekWznHf6h1WwtJfELyFxSPAZ4bnA5t3xOrmUQZ5Q@mail.gmail.com>
Hi Martin
Please consider applying this patch to the kernel.
Regards
Arthur
> -----Original Message-----
> From: Daniil Lunev <dlunev@chromium.org>
> Sent: Wednesday, August 24, 2022 12:36 PM
> To: Arthur Simchaev <Arthur.Simchaev@wdc.com>
> Cc: martin.petersen@oracle.com; linux-scsi@vger.kernel.org; linux-
> kernel@vger.kernel.org; beanhuo@micron.com; Avi Shchislowski
> <Avi.Shchislowski@wdc.com>
> Subject: Re: [PATCH] scsi: ufs-bsg: Remove ufs_bsg_get_query_desc_size
> function
>
> CAUTION: This email originated from outside of Western Digital. Do not click
> on links or open attachments unless you recognize the sender and know that
> the content is safe.
>
>
> Reviewed-by: Daniil Lunev <dlunev@chromium.org>
next prev parent reply other threads:[~2022-09-11 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 12:26 [PATCH] scsi: ufs-bsg: Remove ufs_bsg_get_query_desc_size function Arthur Simchaev
2022-07-17 11:28 ` Arthur Simchaev
2022-07-19 2:53 ` Martin K. Petersen
2022-08-07 23:30 ` Daniil Lunev
2022-08-16 14:32 ` Arthur Simchaev
2022-08-16 14:44 ` Arthur Simchaev
2022-08-24 9:36 ` Daniil Lunev
2022-09-11 10:35 ` Arthur Simchaev [this message]
2022-09-19 8:33 ` Arthur Simchaev
2022-09-20 3:16 ` Martin K. Petersen
2022-09-20 9:38 ` Bean Huo
2022-09-21 9:53 ` Arthur Simchaev
2022-09-28 8:33 ` Arthur Simchaev
2022-09-28 10:36 ` Bean Huo
2022-09-28 14:42 ` Arthur Simchaev
2022-09-28 17:01 ` Arthur Simchaev
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=BY5PR04MB6327C911666B7A5AE0E92A96ED459@BY5PR04MB6327.namprd04.prod.outlook.com \
--to=arthur.simchaev@wdc.com \
--cc=Avi.Shchislowski@wdc.com \
--cc=beanhuo@micron.com \
--cc=dlunev@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.