All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org
Subject: Re: depmod fixes for linux-stable releases
Date: Sun, 10 Jan 2021 18:20:56 +0100	[thread overview]
Message-ID: <CA+icZUX_DBcoPP59FTOQKMJLLLUJyppouLT0oCu2Ji49HepaAg@mail.gmail.com> (raw)
In-Reply-To: <20210110101929.GG4035784@sasha-vm>

On Sun, Jan 10, 2021 at 11:19 AM Sasha Levin <sashal@kernel.org> wrote:
>
> On Sat, Jan 09, 2021 at 05:23:22PM -0800, Linus Torvalds wrote:
> >Ack, I think 436e980e2ed5 ("kbuild: don't hardcode depmod path") is
> >stable material even if it doesn't fix a bug.
> >
> >Not only does the fix for that commit not make sense without the
> >commit in the first place, but any environment that sets depmod
> >somewhere else might well be an environment that still wants stable
> >kernels.
> >
> >It may not be the traditional case, but there's little reason for the
> >kernel build to force that /sbin/depmod location.
>
> I'll take it, thanks!
>

Thanks for pushing (and correcting the stable-ML email-address).

- Sedat -

      reply	other threads:[~2021-01-10 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10  1:18 depmod fixes for linux-stable releases Sedat Dilek
2021-01-10  1:22 ` Fwd: " Sedat Dilek
2021-01-10  1:23 ` Linus Torvalds
2021-01-10 10:19   ` Sasha Levin
2021-01-10 17:20     ` Sedat Dilek [this message]

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=CA+icZUX_DBcoPP59FTOQKMJLLLUJyppouLT0oCu2Ji49HepaAg@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.