From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v1 1/1] MIPS: Alchemy: Remove unused forward declaration
Date: Fri, 13 Jun 2025 13:31:33 +0200 [thread overview]
Message-ID: <aEwMFVSPzc-mV1ve@alpha.franken.de> (raw)
In-Reply-To: <aEv_y5Lfe3Dul48I@smile.fi.intel.com>
On Fri, Jun 13, 2025 at 01:39:07PM +0300, Andy Shevchenko wrote:
> +Cc: Bart.
>
> On Sat, May 31, 2025 at 10:43:46PM +0300, Andy Shevchenko wrote:
> > The 'struct gpio' is not used in the code, remove unneeded forward declaration.
> > This seems to be a leftover for a 5 years.
>
> Any comments on this, please?
looks good
> It prevents us from moving forward with the killing the GPIO legacy APIs
> (it's not critical at all in this case, just an inconvenience for a `grep`,
> but still...).
>
> I think we can take it via GPIO tree if there is no reply.
please do
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2025-06-13 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 19:43 [PATCH v1 1/1] MIPS: Alchemy: Remove unused forward declaration Andy Shevchenko
2025-06-13 10:39 ` Andy Shevchenko
2025-06-13 11:29 ` Manuel Lauss
2025-06-13 12:49 ` Andy Shevchenko
2025-06-13 11:31 ` Thomas Bogendoerfer [this message]
2025-06-13 12:49 ` Andy Shevchenko
2025-06-13 14:16 ` Thomas Bogendoerfer
2025-06-13 21:52 ` Andy Shevchenko
2025-06-24 14:01 ` Andy Shevchenko
2025-07-11 9:42 ` Andy Shevchenko
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=aEwMFVSPzc-mV1ve@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
/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