From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
tzimmermann@suse.de, ojeda@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] auxdisplay: linedisp: Support configuring the boot message
Date: Fri, 31 May 2024 16:43:26 +0300 [thread overview]
Message-ID: <ZlnT_imCNdts8EOd@smile.fi.intel.com> (raw)
In-Reply-To: <CAMuHMdXg1GCAqYPy++4UjFN6QsCnfikZdvsz5=2G4j13E3DUjQ@mail.gmail.com>
On Fri, May 31, 2024 at 10:22:02AM +0200, Geert Uytterhoeven wrote:
> On Fri, May 31, 2024 at 10:16 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Fri, May 31, 2024 at 10:45 AM Geert Uytterhoeven
> > <geert@linux-m68k.org> wrote:
> > > On Fri, May 31, 2024 at 7:28 AM Chris Packham
> > > <chris.packham@alliedtelesis.co.nz> wrote:
> > > > Like we do for charlcd, allow the configuration of the initial message
> > > > on line-display devices.
...
> > > > +#ifndef CONFIG_PANEL_BOOT_MESSAGE
> > > > #include <generated/utsrelease.h>
> > > > +#endif
> > >
> > > The #ifndef/#endif is not really needed.
> >
> > It's needed to avoid unnecessary build of the module (in case of m).
>
> OK.
>
> > > As I see no real deficiencies:
> > > Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
> >
> > I believe you agree with leaving ifdeffery above.
>
> Thanks, I agree to agree ;-)
Btw, I will take a long lasting vacations (ten weeks in a row) and most likely
won't be able to actively participate for this subsystem. Thinking about how
to proceed if something critical appears... Maybe you want a push access to the
same Git repo and in (rare) cases can handle fixes? We may ask Konstantin to
configure that on git.kernel.org.
P.S. This change doesn't seem to me as critical and there is still a chance
that I will have time to proceed, but the situation just motivated me to discuss
the possibilities.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-31 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 23:20 [PATCH] auxdisplay: linedisp: Support configuring the boot message Chris Packham
2024-05-31 7:45 ` Geert Uytterhoeven
2024-05-31 8:16 ` Andy Shevchenko
2024-05-31 8:22 ` Geert Uytterhoeven
2024-05-31 13:43 ` Andy Shevchenko [this message]
2024-05-31 19:12 ` Geert Uytterhoeven
2024-05-31 19:27 ` Andy Shevchenko
2024-05-31 15:35 ` Andy Shevchenko
2024-06-03 21:20 ` Chris Packham
2024-06-03 21:59 ` Chris Packham
2024-06-04 7:27 ` Andy Shevchenko
2024-06-04 7:30 ` 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=ZlnT_imCNdts8EOd@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=geert@linux-m68k.org \
--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