From: Sam Ravnborg <sam@ravnborg.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-fbdev@vger.kernel.org,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: fbdev git tree update
Date: Wed, 2 Feb 2022 18:56:13 +0100 [thread overview]
Message-ID: <YfrFvfZuZM1N9frh@ravnborg.org> (raw)
In-Reply-To: <e1e5b7d1-ea09-6e28-9c39-45b983734a85@gmx.de>
Hi Helge,
On Sun, Jan 30, 2022 at 10:05:39PM +0100, Helge Deller wrote:
> Hello DRI and fbdev developers,
>
> I've now mostly checked all queued-up patches on the fbdev mailing list:
> https://patchwork.kernel.org/project/linux-fbdev/list/
Nice to see all the pending fbdev patches processed.
I do not see why most of them are applied - why bother with
dev_err_probe or spelling fixes in old drivers that does not see any
active development. But that's your call.
How come there are backlight, dt-bindings and agp in between
the fbdev patches?
It would be nice to be able to trust that if the fbdev tree has patches
then it is mentioned when the tree touches files outside the fbdev
dir.
These are the patches that caught my eye:
> Arnd Bergmann (1):
> agp: define proper stubs for empty helpers
>
> Luca Weiss (2):
> backlight: qcom-wled: Add PM6150L compatible
> dt-bindings: simple-framebuffer: allow standalone compatible
>
> Xu Wang (2):
> backlight: lm3630a_bl: Remove redundant 'flush_workqueue()' calls
If this was mentioned then fine - but now it looks like patches that do
not belong here.
Sam
next prev parent reply other threads:[~2022-02-06 0:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 21:05 fbdev git tree update Helge Deller
2022-02-02 17:56 ` Sam Ravnborg [this message]
2022-02-02 18:29 ` Helge Deller
2022-02-02 18:39 ` Sam Ravnborg
2022-02-02 18:49 ` Helge Deller
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=YfrFvfZuZM1N9frh@ravnborg.org \
--to=sam@ravnborg.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).