From: Damien Le Moal <dlemoal@kernel.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: cassel@kernel.org, p.zabel@pengutronix.de,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ata: sata_gemini: Remove unused gemini_sata_reset_bridge()
Date: Thu, 12 Dec 2024 07:53:42 +0900 [thread overview]
Message-ID: <d74c3d02-e4e2-4f78-bf30-3940f50af39b@kernel.org> (raw)
In-Reply-To: <Z1oI6cAAhGrcIVw9@gallifrey>
On 12/12/24 06:49, Dr. David Alan Gilbert wrote:
> * Linus Walleij (linus.walleij@linaro.org) wrote:
>> On Wed, Dec 11, 2024 at 2:12 AM <linux@treblig.org> wrote:
>>
>>> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>>>
>>> gemini_sata_reset_bridge() was added in 2017 by the initial
>>> commit be4e456ed3a5 ("ata: Add driver for Faraday Technology FTIDE010")
>>> but has never been used.
>>>
>>> Remove it.
>>>
>>> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>>
>> Right it was never used because the corresponding reset in
>> the low-level PATA driver didn't work so I patched it out before
>> submitting.
>
> Ah right.
>
>> But should you not also remove sata0_reset and
>> sata1_reset from struct sata_gemini and the code fetching
>> the two reset lines? And even #include <linux/reset.h>?
>
> Oh I see, I was just looking for entirely unreferenced functions
> but that takes a little more following to notice.
>
> I'm happy to do that; are you OK with it as a follow up patch or
> do you want a v2? (And can you test it, I don't have the hardware).
I already applied your previous patch. But I can replace it. So either an
incremental patch or a v2 is fine with me. Thanks.
>
> Dave
>
>> Yours,
>> Linus Walleij
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-12-11 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 1:12 [PATCH] ata: sata_gemini: Remove unused gemini_sata_reset_bridge() linux
2024-12-11 4:23 ` Damien Le Moal
2024-12-11 10:34 ` Linus Walleij
2024-12-11 21:49 ` Dr. David Alan Gilbert
2024-12-11 22:53 ` Damien Le Moal [this message]
2024-12-11 23:53 ` Dr. David Alan Gilbert
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=d74c3d02-e4e2-4f78-bf30-3940f50af39b@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=p.zabel@pengutronix.de \
/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