mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Winiarska, Iwona" <iwona.winiarska@intel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] PECI fixes for v6.4
Date: Thu, 1 Jun 2023 09:44:47 +0100	[thread overview]
Message-ID: <2023060125-reconvene-prankster-c014@gregkh> (raw)
In-Reply-To: <1693fe7002af39c4efc899a6e60dbafc906d6b25.camel@intel.com>

On Thu, Jun 01, 2023 at 08:34:21AM +0000, Winiarska, Iwona wrote:
> On Mon, 2023-05-29 at 14:53 +0100, gregkh@linuxfoundation.org wrote:
> > On Mon, May 22, 2023 at 09:24:26PM +0000, Winiarska, Iwona wrote:
> > > Hi Greg,
> > > 
> > > please pull PECI update for Linux v6.4.
> > > 
> > > Thanks
> > > -Iwona
> > > 
> > > The following changes since commit c21c0f9a20a963f5a1874657a4e3d657503f7815:
> > > 
> > >   Binder: Add async from to transaction record (2023-05-13 20:38:12 +0900)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/iwi/linux.git tags/peci-
> > > fixes-6.4
> > 
> > This includes some random Binder changes that do not belong in my
> > char-misc-linus branch right now for 6.4-final
> 
> Sorry - I based it on char-misc-testing / char-misc-next.
> 
> > 
> > > 
> > > for you to fetch changes up to 849b391254bf64796655868dbb6dee23551ff7d3:
> > > 
> > >   peci: Constify struct peci_controller_ops (2023-05-22 22:16:16 +0200)
> > 
> > Why is this a bugfix that needs to get merged now?  Shouldn't this be
> > for 6.5-rc1?
> 
> It's a small fix - it can wait for 6.5-rc1.

Great, send it now as a patch?

thanks,

greg k-h

      reply	other threads:[~2023-06-01  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 21:24 Winiarska, Iwona
2023-05-29 13:53 ` gregkh
2023-06-01  8:34   ` Winiarska, Iwona
2023-06-01  8:44     ` gregkh [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=2023060125-reconvene-prankster-c014@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=iwona.winiarska@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.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®