From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] MIPS: Alchemy: Remove unused forward declaration
Date: Wed, 15 Jul 2026 17:44:44 +0200 [thread overview]
Message-ID: <aleq7AHSEG7H1asl@alpha.franken.de> (raw)
In-Reply-To: <alelCeG0r8c8Mq94@ashevche-desk.local>
On Wed, Jul 15, 2026 at 06:19:37PM +0300, Andy Shevchenko wrote:
> On Wed, Jul 15, 2026 at 08:08:00AM -0700, Bartosz Golaszewski wrote:
> > On Wed, 15 Jul 2026 17:03:48 +0200, Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> said:
>
> ...
>
> > > Cc: Bartosz Golaszewski <brgl@kernel.org>
> > >
> > > This patch is floating around for more than a year without anybody
> > > taking it! Please, please, do something about this. Since it has
> > > an ack by MIPS maintainer, Bart, can you just pick this up?
>
> > Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
>
> Thanks, and sorry for the noise, I was cleaning an old branch and actually this
> had been applied already. Sorry again, I need some vacation (which will happen
> in a week).
d1d0aa620a0f MIPS: Alchemy: Remove unused forward declaration
I took it last merge window, or do I miss something ?
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:[~2026-07-15 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:03 [PATCH v3 1/1] MIPS: Alchemy: Remove unused forward declaration Andy Shevchenko
2026-07-15 15:08 ` Bartosz Golaszewski
2026-07-15 15:19 ` Andy Shevchenko
2026-07-15 15:44 ` Thomas Bogendoerfer [this message]
2026-07-15 16:01 ` 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=aleq7AHSEG7H1asl@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.