From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Palmer <daniel@thingy.jp>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
sudipm.mukherjee@gmail.com, joerg@dorchain.net,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] parport: mfc3: Convert to a modern zorro driver
Date: Tue, 31 Mar 2026 12:13:32 +0300 [thread overview]
Message-ID: <acuQPP5TKLZyuiK6@ashevche-desk.local> (raw)
In-Reply-To: <CAFr9PXmF+311dNrFd-xmzyMuQoZV95DvZRTauoHHZCzR-5piFw@mail.gmail.com>
On Tue, Mar 31, 2026 at 06:09:12PM +0900, Daniel Palmer wrote:
> On Mon, 30 Mar 2026 at 19:02, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> Thank you for the review. It seems like the parport maintainer isn't
> responding (Andy has some patches that haven't been reviewed or picked
> up[0] too).
> Is there a way to take this via the m68k tree because it only matters
> for m68k or something?
>
> I have CC'd Linus, Greg K-H and Andy. After googling "LKML how to
> escalate unresponsive maintainer" and not finding much. If this is
> wrong, sorry for the spam. :)
Become a new maintainer!
But you can also send a patch changing MAINTAINERS database.
> 0 - https://lore.kernel.org/lkml/20260122090601.2380747-1-andriy.shevchenko@linux.intel.com/
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-03-31 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 10:16 Daniel Palmer
2026-03-30 10:02 ` Geert Uytterhoeven
2026-03-31 9:09 ` Daniel Palmer
2026-03-31 9:13 ` Andy Shevchenko [this message]
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=acuQPP5TKLZyuiK6@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=joerg@dorchain.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®