public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Kees Cook" <keescook@chromium.org>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Anil Gurumurthy" <anil.gurumurthy@qlogic.com>,
	"Sudarsana Kalluru" <sudarsana.kalluru@qlogic.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"Azeem Shaikh" <azeemshaikh38@gmail.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] scsi: bfa: fix function pointer type mismatch for state machines
Date: Wed, 21 Jun 2023 20:42:10 +0200	[thread overview]
Message-ID: <336f2156-220f-47ff-be97-5a2a9c475372@app.fastmail.com> (raw)
In-Reply-To: <202306211131.18885FF471@keescook>

On Wed, Jun 21, 2023, at 20:33, Kees Cook wrote:
> On Fri, Jun 16, 2023 at 11:22:10AM +0200, Arnd Bergmann wrote:
>> 
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Thanks for all this! It's a lot of mechanical changes, but looks correct
> to me. One nit below...
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
>
>> [...]
>>  static void
>> -bfad_sm_uninit(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_uninit(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_created(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_created(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_initializing(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_initializing(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_operational(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_operational(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_stopping(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_stopping(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_failed(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_failed(struct bfad_s *bfad, enum bfad_sm_event);
>>  static void
>> -bfad_sm_fcs_exit(struct bfad_s *bfad, enum bfad_sm_event event);
>> +bfad_sm_fcs_exit(struct bfad_s *bfad, enum bfad_sm_event);
>
> This bit doesn't seem needed? i.e. why remove the prototype's argument
> names?

Right, my mistake. I went through a few revisions and first tried to
change the prototypes here, but later changed them back. I missed
this after I folded my intermediate steps back into a single patch.

    Arnd

  reply	other threads:[~2023-06-21 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  9:22 [PATCH 1/2] scsi: bfa: fix function pointer type mismatch for hcb_qe->cbfn Arnd Bergmann
2023-06-16  9:22 ` [PATCH 2/2] scsi: bfa: fix function pointer type mismatch for state machines Arnd Bergmann
2023-06-21 18:33   ` Kees Cook
2023-06-21 18:42     ` Arnd Bergmann [this message]
2023-06-21 18:33 ` [PATCH 1/2] scsi: bfa: fix function pointer type mismatch for hcb_qe->cbfn Kees Cook

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=336f2156-220f-47ff-be97-5a2a9c475372@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=anil.gurumurthy@qlogic.com \
    --cc=arnd@kernel.org \
    --cc=azeemshaikh38@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=jejb@linux.ibm.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sudarsana.kalluru@qlogic.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