From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
Sathya Prakash <sathya.prakash@broadcom.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>
Subject: Re: [PATCH] scsi: mpi3mr: Fix SATA NCQ priority support
Date: Thu, 6 Jun 2024 05:34:35 -0700 [thread overview]
Message-ID: <ZmGs2wZDO9ZTO0s4@infradead.org> (raw)
In-Reply-To: <a61c0dc6-40f3-4e01-9657-eadbf3a50c99@kernel.org>
On Thu, Jun 06, 2024 at 09:14:46PM +0900, Damien Le Moal wrote:
> "also" ? your previous point was not about this function ?
No, about all the attribute boilerplate code.
next prev parent reply other threads:[~2024-06-06 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 5:47 [PATCH] scsi: mpi3mr: Fix SATA NCQ priority support Damien Le Moal
2024-06-06 9:31 ` Christoph Hellwig
2024-06-06 12:14 ` Damien Le Moal
2024-06-06 12:34 ` Christoph Hellwig [this message]
2024-06-06 23:16 ` Damien Le Moal
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=ZmGs2wZDO9ZTO0s4@infradead.org \
--to=hch@infradead.org \
--cc=dlemoal@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.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