From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] scsi: Rename .slave_alloc() and .slave_destroy()
Date: Thu, 3 Oct 2024 07:26:01 +0900 [thread overview]
Message-ID: <9adb1b8a-5b46-42da-81c3-76c8ed50f3c1@kernel.org> (raw)
In-Reply-To: <376dfcb4-a25d-457d-acdd-4af77290b05b@acm.org>
On 10/3/24 05:23, Bart Van Assche wrote:
> On 9/30/24 5:10 PM, Damien Le Moal wrote:
>> On 10/1/24 05:18, Bart Van Assche wrote:
>>> diff --git a/include/linux/libata.h b/include/linux/libata.h
>>> index 9b4a6ff03235..e04184b6d79b 100644
>>> --- a/include/linux/libata.h
>>> +++ b/include/linux/libata.h
>>> @@ -1201,10 +1201,10 @@ extern int ata_std_bios_param(struct scsi_device *sdev,
>>> struct block_device *bdev,
>>> sector_t capacity, int geom[]);
>>> extern void ata_scsi_unlock_native_capacity(struct scsi_device *sdev);
>>> -extern int ata_scsi_slave_alloc(struct scsi_device *sdev);
>>> +extern int ata_scsi_device_alloc(struct scsi_device *sdev);
>>
>> While at it, drop the extern.
>>
>>> int ata_scsi_device_configure(struct scsi_device *sdev,
>>> struct queue_limits *lim);
>>> -extern void ata_scsi_slave_destroy(struct scsi_device *sdev);
>>> +extern void ata_scsi_device_destroy(struct scsi_device *sdev);
>>
>> Here too.
>
> Hi Damien,
>
> Can I declare removing superfluous "extern" keywords as out-of-scope for
> this patch series? There are plenty of superfluous "extern" keywords in
> many Linux .h files. Removing the superfluous "extern" keyword for the
> functions renamed by this patch series only probably won't make much of
> a difference.
That is fine.
>
> Thanks,
>
> Bart.
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-10-02 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 20:18 [PATCH 0/4] Do not use "slave" in function names Bart Van Assche
2024-09-30 20:18 ` [PATCH 1/4] scsi: Rename .slave_alloc() and .slave_destroy() Bart Van Assche
2024-09-30 20:58 ` Matthew Wilcox
2024-09-30 21:10 ` Bart Van Assche
2024-10-01 0:10 ` Damien Le Moal
2024-10-02 20:23 ` Bart Van Assche
2024-10-02 22:26 ` Damien Le Moal [this message]
2024-10-01 3:26 ` Randy Dunlap
2024-10-01 4:43 ` Randy Dunlap
2024-10-01 20:15 ` Bart Van Assche
2024-09-30 20:18 ` [PATCH 2/4] scsi: Convert SCSI drivers to .device_configure() Bart Van Assche
2024-10-01 6:11 ` Leon Romanovsky
2024-10-02 9:02 ` Geoff Levand
2024-10-02 15:19 ` Khalid Aziz
2024-09-30 20:18 ` [PATCH 3/4] scsi: core: Remove .slave_configure() Bart Van Assche
2024-09-30 20:18 ` [PATCH 4/4] scsi: core: Update .slave_configure() references in the documentation 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=9adb1b8a-5b46-42da-81c3-76c8ed50f3c1@kernel.org \
--to=dlemoal@kernel.org \
--cc=bvanassche@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox