public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-kernel@vger.kernel.org,
	Javier Martinez Canillas <javierm@redhat.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v2 1/3] auxdisplay: Take over maintainership, but in Odd Fixes mode
Date: Mon, 12 Feb 2024 18:43:47 +0200	[thread overview]
Message-ID: <ZcpKwz8J8OoODMYl@smile.fi.intel.com> (raw)
In-Reply-To: <ZcpKh_EgNM5IaV-P@smile.fi.intel.com>

On Mon, Feb 12, 2024 at 06:42:48PM +0200, Andy Shevchenko wrote:
> On Mon, Feb 12, 2024 at 05:33:39PM +0100, Thomas Zimmermann wrote:
> > Am 12.02.24 um 14:23 schrieb Andy Shevchenko:
> > > I have no time for this, but since it looks like I'm the main
> > > contributor for the last few years to the subsystem, I'll take
> > > it for now. Geert agreed to help me with as a designated reviwer.
> > > Let's see how it will go...
> > 
> > A few days ago, I talked to Javier about how auxdisplay is a hotchpodge of
> > various drivers that seem to belong into other subsystems. Could we attempt
> > to move all drivers into other places and then remove the auxdisplay
> > subsystem?
> 
> Can you be more precise on how it can be done? We have at least two clusters of
> the displays: line-display and HD44780-based ones. Moreover, the latter might
> use the former in the future (in some cases).

Btw, I have no time for major things here, if you wish, please take over,
I will be happy to get rid of this.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-02-12 16:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 13:23 [PATCH v2 0/3] auxdisplay: Refresh MAINTAINERS for the subsystem Andy Shevchenko
2024-02-12 13:23 ` [PATCH v2 1/3] auxdisplay: Take over maintainership, but in Odd Fixes mode Andy Shevchenko
2024-02-12 13:36   ` Andy Shevchenko
2024-02-12 13:43     ` Geert Uytterhoeven
2024-02-12 13:46       ` Andy Shevchenko
2024-02-12 16:33   ` Thomas Zimmermann
2024-02-12 16:42     ` Andy Shevchenko
2024-02-12 16:43       ` Andy Shevchenko [this message]
2024-02-13  8:10         ` Javier Martinez Canillas
2024-02-13 12:11           ` Miguel Ojeda
2024-02-13 14:55           ` Andy Shevchenko
2024-02-13  8:28       ` Thomas Zimmermann
2024-02-13  8:34         ` Geert Uytterhoeven
2024-02-12 22:33   ` Miguel Ojeda
2024-02-12 13:23 ` [PATCH v2 2/3] auxdisplay: Move cfag12864b.h to the subsystem folder Andy Shevchenko
2024-02-12 13:36   ` Andy Shevchenko
2024-02-14 16:58     ` Geert Uytterhoeven
2024-02-14 17:15       ` Miguel Ojeda
2024-02-14 17:40         ` Andy Shevchenko
2024-02-14 17:42           ` Miguel Ojeda
2024-02-14 17:50             ` Andy Shevchenko
2024-02-14 18:48               ` Geert Uytterhoeven
2024-02-14 18:48               ` Miguel Ojeda
2024-02-14 18:54                 ` Andy Shevchenko
2024-02-14 18:57                   ` Andy Shevchenko
2024-02-12 13:23 ` [PATCH v2 3/3] auxdisplay: Add 7 and 14 segment mappings to MAINTAINERS Andy Shevchenko
2024-02-14 17:00   ` Geert Uytterhoeven
2024-02-12 13:37 ` [PATCH v2 0/3] auxdisplay: Refresh MAINTAINERS for the subsystem Andy Shevchenko
2024-02-13 16:47 ` 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=ZcpKwz8J8OoODMYl@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=geert@linux-m68k.org \
    --cc=javierm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=tzimmermann@suse.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