From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Maxime Ripard" <maxime@cerno.tech>,
"Noralf Trønnes" <noralf@tronnes.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 4/4] MAINTAINERS: Add entry for Solomon SSD1307 OLED displays DRM driver
Date: Tue, 1 Feb 2022 11:32:04 +0200 [thread overview]
Message-ID: <Yfj+FOELlbtdhvRa@smile.fi.intel.com> (raw)
In-Reply-To: <20220131201537.2325487-1-javierm@redhat.com>
On Mon, Jan 31, 2022 at 09:15:37PM +0100, Javier Martinez Canillas wrote:
> To make sure that tools like the get_maintainer.pl script will suggest
> to Cc me if patches are posted for this driver.
>
> Also include the Device Tree binding for the old ssd1307fb fbdev driver
> since the new DRM driver was made compatible with the existing binding.
Dunno why you have patches 3 and 4 missed references (in terms of email
thread).
> +DRM DRIVER FOR SOLOMON SSD1307 OLED DISPLAYS
> +M: Javier Martinez Canillas <javierm@redhat.com>
> +S: Maintained
> +T: git git://anongit.freedesktop.org/drm/drm-misc
> +F: Documentation/devicetree/bindings/display/solomon,ssd1307fb.yaml
> +F: drivers/gpu/drm/tiny/ssd1307.c
I think it makes sense to add ssd1307fb as well. At least you may point out
people patching old driver about new one until it's gone completely.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-02-01 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:15 [PATCH 4/4] MAINTAINERS: Add entry for Solomon SSD1307 OLED displays DRM driver Javier Martinez Canillas
[not found] ` <YfhKrznFzRmDcZa6@ravnborg.org>
2022-01-31 23:24 ` Javier Martinez Canillas
2022-02-01 9:32 ` Andy Shevchenko [this message]
2022-02-01 11:17 ` Javier Martinez Canillas
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=Yfj+FOELlbtdhvRa@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.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