From: Lee Jones <lee@kernel.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
deller@gmx.de, kherbst@redhat.com, lyude@redhat.com,
dakr@redhat.com, daniel@ffwll.ch, airlied@gmail.com,
gregkh@linuxfoundation.org,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 1/9] backlight/corgi-lcd: Include <linux/backlight.h>
Date: Mon, 26 Feb 2024 12:52:09 +0000 [thread overview]
Message-ID: <20240226125209.GB23065@google.com> (raw)
In-Reply-To: <62ad32cb-3fd1-4c21-ab2c-a194e559d12a@suse.de>
On Mon, 26 Feb 2024, Thomas Zimmermann wrote:
> Hi
>
> Am 26.02.24 um 13:33 schrieb Lee Jones:
> > On Mon, 26 Feb 2024, Jani Nikula wrote:
> >
> > > On Fri, 23 Feb 2024, Lee Jones <lee@kernel.org> wrote:
> > > > On Wed, 21 Feb 2024, Thomas Zimmermann wrote:
> > > >
> > > > > cc'ing backlight maintainers
> > > > I cannot review/accept patches like this.
> > > >
> > > > Please submit a [RESEND].
> > > I bounced the original [1] to you. Please consider acking to merge the
> > > one-line #include addition via fbdev so we don't have to respin the
> > > series for no good reason.
> > The "good reason" would be that it was not sent properly in the first
> > place. My kernel.org mail is filtered by the recipients headers. If
> > the original wasn't sent to me, bouncing won't work either. I've since
> > reviewed the patch and seen the set on LORE. This is non-optimal.
> > Please use get_maintainer.pl next time.
> >
> > This time only, patch is:
> >
> > Acked-by: Lee Jones <lee@kernel.org>
>
> No problem, I'll send out another series. I just didn't get to do it.
No need to do that now on my behalf. You have my Ack.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-02-26 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:37 [PATCH v3 0/9] fbdev: Clean up include dependencies in header Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 1/9] backlight/corgi-lcd: Include <linux/backlight.h> Thomas Zimmermann
2024-02-21 10:29 ` Thomas Zimmermann
2024-02-23 10:56 ` Lee Jones
2024-02-26 11:42 ` Jani Nikula
2024-02-26 12:33 ` Lee Jones
2024-02-26 12:48 ` Thomas Zimmermann
2024-02-26 12:52 ` Lee Jones [this message]
2024-02-19 9:37 ` [PATCH v3 2/9] drm/nouveau: " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 3/9] staging/fbtft: " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 4/9] fbdev: Do not include <linux/backlight.h> in header Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 5/9] fbdev: Do not include <linux/fs.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 6/9] fbdev: Do not include <linux/notifier.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 7/9] fbdev: Do not include <linux/slab.h> " Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 8/9] fbdev: Clean up forward declarations in header file Thomas Zimmermann
2024-02-19 9:37 ` [PATCH v3 9/9] fbdev: Clean up include statements " Thomas Zimmermann
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=20240226125209.GB23065@google.com \
--to=lee@kernel.org \
--cc=airlied@gmail.com \
--cc=dakr@redhat.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=jingoohan1@gmail.com \
--cc=kherbst@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).