linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Dan Murphy <dmurphy@ti.com>,
	Amireddy Mallikarjuna reddy 
	<mallikarjunax.reddy@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-leds <linux-leds@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] leds: LEDS_BLINK_LGM should depend on X86
Date: Mon, 26 Apr 2021 09:06:16 +0200	[thread overview]
Message-ID: <CAMuHMdW_Mf49yLVt+BJjNNLi+H5C-qaaWFfjQNBr5iuSo25xZQ@mail.gmail.com> (raw)
In-Reply-To: <20210425205717.GD10996@amd>

Hi Pavel,

On Sun, Apr 25, 2021 at 10:57 PM Pavel Machek <pavel@ucw.cz> wrote:
> > The Intel Lightning Mountain (LGM) Serial Shift Output controller (SSO)
> > is only present on Intel Lightning Mountain SoCs.  Hence add a
> > dependency on X86, to prevent asking the user about this driver when
> > configuring a kernel without Intel Lightning Mountain platform support.
> >
> > While at it, merge the other dependencies into a single statement.
> >
> > Fixes: c3987cd2bca34ddf ("leds: lgm: Add LED controller driver for LGM SoC")
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> This rejected, so I applied it by hand.

Thank you!

> I'm deleting the Fixes tag --
> we don't want this in stable.

Why not? Shouldn't people running stable be shielded from useless
questions while configuring their kernels?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-04-26  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 13:39 [PATCH] leds: LEDS_BLINK_LGM should depend on X86 Geert Uytterhoeven
2021-04-25 20:57 ` Pavel Machek
2021-04-26  7:06   ` Geert Uytterhoeven [this message]
2021-04-27  9:12     ` Pavel Machek

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=CAMuHMdW_Mf49yLVt+BJjNNLi+H5C-qaaWFfjQNBr5iuSo25xZQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=arnd@arndb.de \
    --cc=dmurphy@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mallikarjunax.reddy@linux.intel.com \
    --cc=pavel@ucw.cz \
    /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).