mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	John Ogness <john.ogness@linutronix.de>
Subject: Re: Please queue ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() for stable (was: Re: [PATCH] ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans())
Date: Thu, 30 Apr 2020 09:41:07 +0200 (CEST)	[thread overview]
Message-ID: <1750032835.172217.1588232467635.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20200430071137.GA2382543@kroah.com>

----- Ursprüngliche Mail -----
>> I always thought havings a Fixes-Tag is enough to make sure it will
>> get picked up. Isn't this the case?
> 
> No it is not, please read:
>    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
> 
> Our scripts are doing better to dig out stuff where maintainers mess up
> and forget to put the cc: stable tag, but you can never rely on it.
> Please stick with the above rules that have been there for 15+ years :)

Sir, yes, sir.

Thanks,
//richard

      reply	other threads:[~2020-04-30  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 21:52 [PATCH] ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() Richard Weinberger
2020-04-29 14:56 ` John Ogness
2020-04-29 15:03   ` Richard Weinberger
2020-04-29 18:51   ` Please queue ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() for stable (was: Re: [PATCH] ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()) Richard Weinberger
2020-04-30  7:11     ` Greg KH
2020-04-30  7:41       ` Richard Weinberger [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=1750032835.172217.1588232467635.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=stable@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
all inboxes | Powered by JetHome®