From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
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: Tue, 24 Jun 2025 17:01:28 +0300 [thread overview]
Message-ID: <aFqvuIzH2zo5X76q@smile.fi.intel.com> (raw)
In-Reply-To: <aEydkh4EkKu6w2NJ@surfacebook.localdomain>
On Sat, Jun 14, 2025 at 12:52:18AM +0300, Andy Shevchenko wrote:
> Fri, Jun 13, 2025 at 04:16:57PM +0200, Thomas Bogendoerfer kirjoitti:
> > On Fri, Jun 13, 2025 at 03:49:41PM +0300, Andy Shevchenko wrote:
> > > On Fri, Jun 13, 2025 at 01:31:33PM +0200, Thomas Bogendoerfer wrote:
> > > > On Fri, Jun 13, 2025 at 01:39:07PM +0300, Andy Shevchenko wrote:
> > > > > On Sat, May 31, 2025 at 10:43:46PM +0300, Andy Shevchenko wrote:
...
> > > > > I think we can take it via GPIO tree if there is no reply.
> > > >
> > > > please do
> > >
> > > Acked-by?
> >
> > Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
>
> Thank you! Bart, seems we are all set to route this via GPIO tree. Do you have
> any objections?
Bart, can you apply this one, please? Or do you have objections?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-06-24 14:01 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
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 [this message]
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=aFqvuIzH2zo5X76q@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.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