From: Damien Le Moal <dlemoal@kernel.org>
To: Louis Sautier <sautier.louis@gmail.com>
Cc: Sathya Prakash <sathya.prakash@broadcom.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Ranjan Kumar <ranjan.kumar@broadcom.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Guenter Roeck <linux@roeck-us.net>,
MPT-FusionLinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 1/2] scsi: mpt3sas: add IO Unit Page 7 config accessor
Date: Fri, 12 Jun 2026 08:32:17 +0900 [thread overview]
Message-ID: <8171d9e5-e347-403a-bc3c-79a89a8e45d3@kernel.org> (raw)
In-Reply-To: <airkbg8-kDC0Gyv9@localhost>
On 6/12/26 01:38, Louis Sautier wrote:
> On Wed, 10 Jun 2026 08:12:05 +0800, Damien Le Moal wrote:
>>> +int
>>> +mpt3sas_config_get_iounit_pg7(struct MPT3SAS_ADAPTER *ioc,
>>
>> Please do not break the line after "int"
>
> Hi and thanks for the review.
>
> Sure, I can change this. Can you confirm we want to diverge from the
> convention used by neighbouring functions such as
> mpt3sas_config_get_iounit_pg8?
My comment is based on the standard kernel coding style, which we should follow.
>
>>> + Mpi2ConfigReply_t *mpi_reply, Mpi2IOUnitPage7_t *config_page)
>>> +{
>>> + Mpi2ConfigRequest_t mpi_request;
>>> + int r;
>>> +
>>> + memset(&mpi_request, 0, sizeof(Mpi2ConfigRequest_t));
>>> + mpi_request.Function = MPI2_FUNCTION_CONFIG;
>>> + mpi_request.Action = MPI2_CONFIG_ACTION_PAGE_HEADER;
>>> + mpi_request.Header.PageType = MPI2_CONFIG_PAGETYPE_IO_UNIT;
>>> + mpi_request.Header.PageNumber = 7;
>>> + mpi_request.Header.PageVersion = MPI2_IOUNITPAGE7_PAGEVERSION;
>>> + ioc->build_zero_len_sge_mpi(ioc, &mpi_request.PageBufferSGE);
>>> + r = _config_request(ioc, &mpi_request, mpi_reply,
>>> + MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT, NULL, 0);
>>
>> r = _config_request(ioc, &mpi_request, mpi_reply,
>> MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT, NULL, 0);
>>
>> is a lot nicer to read.
>
> Do I also align the signature like so in both the source file and the
> header?
I think so, as in my opinion, that makes for a nicer reading.
>
> int mpt3sas_config_get_iounit_pg7(struct MPT3SAS_ADAPTER *ioc,
> Mpi2ConfigReply_t *mpi_reply,
> Mpi2IOUnitPage7_t *config_page)
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-06-11 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:44 [PATCH v3 RESEND 0/2] scsi: mpt3sas: add hwmon support Louis Sautier
2026-06-09 16:44 ` [PATCH v3 RESEND 1/2] scsi: mpt3sas: add IO Unit Page 7 config accessor Louis Sautier
2026-06-09 16:55 ` sashiko-bot
2026-06-10 0:12 ` Damien Le Moal
2026-06-11 16:38 ` Louis Sautier
2026-06-11 23:32 ` Damien Le Moal [this message]
2026-06-09 16:44 ` [PATCH v3 RESEND 2/2] scsi: mpt3sas: add hwmon support Louis Sautier
2026-06-09 16:54 ` sashiko-bot
2026-06-10 0:22 ` Damien Le Moal
2026-06-11 16:39 ` Louis Sautier
2026-06-11 23:34 ` 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=8171d9e5-e347-403a-bc3c-79a89a8e45d3@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=martin.petersen@oracle.com \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sautier.louis@gmail.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 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.