Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: stable@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v5.4.y 1/3] driver: platform: Add helper for safer setting of driver_override
Date: Mon, 23 Oct 2023 12:07:36 +0200	[thread overview]
Message-ID: <2023102307-passably-scallion-ad80@gregkh> (raw)
In-Reply-To: <20231023094815.GE8909@google.com>

On Mon, Oct 23, 2023 at 10:48:15AM +0100, Lee Jones wrote:
> On Fri, 20 Oct 2023, Greg Kroah-Hartman wrote:
> 
> > <snip>
> > 
> > Something went wrong with this 5.4 series you sent, I got the following
> > emails which look like 2 different versions of this series?:
> > 
> >   11   C Oct 18 Lee Jones       (7.0K) [PATCH v5.4.y 1/3] driver: platform: Add helper for safer setting of driver_override
> >   12   C Oct 18 Lee Jones       (2.6K) ├─>[PATCH v5.4.y 3/3] rpmsg: Fix kfree() of static memory on setting driver_override
> >   13   C Oct 18 Lee Jones       (1.1K) ├─>[PATCH v5.4.y 2/3] rpmsg: Constify local variable in field store macro
> >   14   C Oct 18 Lee Jones       (2.6K) ├─>[PATCH v5.4.y 2/2] rpmsg: Fix kfree() of static memory on setting driver_override
> >   15   C Oct 18 Lee Jones       (1.1K) └─>[PATCH v5.4.y 1/2] rpmsg: Constify local variable in field store macro
> > 
> > And you can see it here:
> > 	https://lore.kernel.org/all/20231018120527.2110438-1-lee@kernel.org/#r
> > 
> > So I don't know what patches to take for 5.4, sorry.  Can you please resend the
> > properly ones?
> 
> You're right.  They're in my inbox too.
> 
> One set was sent 1s after the other, so must be a tooling error.
> 
> The 2 sets are identical.
> 
> 1/3 == 1/3
> 2/3 == 2/3
> 3/3 == 3/3

You have 1/2 and 2/2 here, so hence my confusion :(

All of these need to be resent anyway, let's talk off-list...

thanks,

greg k-h

      reply	other threads:[~2023-10-23 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 12:05 [PATCH v5.4.y 1/3] driver: platform: Add helper for safer setting of driver_override Lee Jones
2023-10-18 12:05 ` [PATCH v5.4.y 1/2] rpmsg: Constify local variable in field store macro Lee Jones
2023-10-18 12:05 ` [PATCH v5.4.y 2/3] " Lee Jones
2023-10-18 12:05 ` [PATCH v5.4.y 2/2] rpmsg: Fix kfree() of static memory on setting driver_override Lee Jones
2023-10-18 12:05 ` [PATCH v5.4.y 3/3] " Lee Jones
2023-10-20 16:07 ` [PATCH v5.4.y 1/3] driver: platform: Add helper for safer setting of driver_override Greg Kroah-Hartman
2023-10-23  9:48   ` Lee Jones
2023-10-23 10:07     ` Greg Kroah-Hartman [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=2023102307-passably-scallion-ad80@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lee@kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --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