All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sasha Levin <sashal@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	stable-commits@vger.kernel.org, "Shawn Guo" <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Mark Brown" <broonie@kernel.org>,
	"NXP Linux Team" <linux-imx@nxp.com>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	stable@vger.kernel.org
Subject: Re: Patch "spi: imx: add a device specific prepare_message callback" has been added to the 4.19-stable tree
Date: Sat, 9 Dec 2023 12:29:55 +0100	[thread overview]
Message-ID: <2023120959-buffer-amendment-77cf@gregkh> (raw)
In-Reply-To: <ZXQKi4QvI7KOJsyb@sashalap>

On Sat, Dec 09, 2023 at 01:34:51AM -0500, Sasha Levin wrote:
> On Fri, Dec 08, 2023 at 11:48:38AM +0100, Uwe Kleine-König wrote:
> > Hello,
> > 
> > On Fri, Dec 08, 2023 at 05:08:32AM -0500, Sasha Levin wrote:
> > > This is a note to let you know that I've just added the patch titled
> > > 
> > >     spi: imx: add a device specific prepare_message callback
> > > 
> > > to the 4.19-stable tree which can be found at:
> > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > > 
> > > The filename of the patch is:
> > >      spi-imx-add-a-device-specific-prepare_message-callba.patch
> > > and it can be found in the queue-4.19 subdirectory.
> > > 
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > > 
> > > 
> > > 
> > > commit b19a3770ce84da3c16acc7142e754cd8ff80ad3d
> > > Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > Date:   Fri Nov 30 07:47:05 2018 +0100
> > > 
> > >     spi: imx: add a device specific prepare_message callback
> > > 
> > >     [ Upstream commit e697271c4e2987b333148e16a2eb8b5b924fd40a ]
> > > 
> > >     This is just preparatory work which allows to move some initialisation
> > >     that currently is done in the per transfer hook .config to an earlier
> > >     point in time in the next few patches. There is no change in behaviour
> > >     introduced by this patch.
> > > 
> > >     Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > >     Signed-off-by: Mark Brown <broonie@kernel.org>
> > >     Signed-off-by: Sasha Levin <sashal@kernel.org>
> > 
> > The patch alone shouldn't be needed for stable and there is no
> > indication that it's a dependency for another patch. Is this an
> > oversight?
> 
> It is, appologies. I've been traveling and my patch-shuffling-fu isn't
> doing well with conference/jetlag.
> 
> This is a dependency for 00b80ac93553 ("spi: imx: mx51-ecspi: Move some
> initialisation to prepare_message hook.").
> 
> > Other than that: IMHO the subject for this type of report could be improved. Currently it's:
> > 
> > 	Subject: Patch "spi: imx: add a device specific prepare_message callback" has been added to the 4.19-stable tree
> > 
> > The most important part of it is "4.19-stable", but that only appears
> > after character column 90 and so my MUA doesn't show it unless the
> > window is wider than my default setting. Maybe make this:
> > 
> > 	Subject: for-stable-4.19: "spi: imx: add a device specific prepare_message callback"
> > 
> > ?
> 
> I borrowed the format from Greg, and I'd say that if we make changes
> then we should be consistent with eachother.

Sure, I can change my script, but better yet, can you send a patch
against this file:
	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/scripts/added-to-stable

> No objections on my end; maybe I'd even go further and try and send one
> email per patch rather than one mail per patch/tree.

one-per-patch isn't going to work, sorry, as I push out queues
separately.

> Or... finally drop the stable-commits mailing list altogether? Does
> anyone still need this (vs. just looking at -rcs)?
> 
> Greg?

Yes, we still need it, we want a public record of what is merged, and
that is what the mailing list archives provide.

thanks,

greg k-h

      reply	other threads:[~2023-12-09 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231208100833.2847199-1-sashal@kernel.org>
2023-12-08 10:48 ` Patch "spi: imx: add a device specific prepare_message callback" has been added to the 4.19-stable tree Uwe Kleine-König
2023-12-09  6:34   ` Sasha Levin
2023-12-09 11:29     ` Greg KH [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=2023120959-buffer-amendment-77cf@gregkh \
    --to=greg@kroah.com \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sashal@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.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 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.