mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Winiarska, Iwona" <iwona.winiarska@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] PECI changes for v7.4-rc1
Date: Fri, 25 Sep 2026 21:20:59 +0000	[thread overview]
Message-ID: <14b83bcafac21987132c08a23043254c6c43e3ec.camel@intel.com> (raw)

Hi Greg!

Please pull PECI update for Linux v7.4.

Thanks
-Iwona

The following changes since commit 93f51579e7df248780214094418f205253383cc5:

  Linux 7.3-rc4 (2026-09-20 13:48:15 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iwi/linux.git tags/peci-next-7.4-rc1

for you to fetch changes up to 425125e6d408b5969afb99c3e95a391f1f1ad81d:

  peci: npcm: Initialize state before requesting IRQ (2026-09-25 22:20:38 +0200)

----------------------------------------------------------------
Update peci-next for v7.4-rc1

Small fixes in controller drivers including:
- fix for uninitialized clk_init_data structure (peci-aspeed),
- moving lock and completion initializations before registering
  interrupt handler to avoid using them uninitialized (peci-aspeed,
  peci-npcm).

----------------------------------------------------------------
Geert Uytterhoeven (1):
      peci: controller: aspeed: Make sure clk_init_data is fully initialized

Runyu Xiao (2):
      peci: aspeed: Initialize state before requesting IRQ
      peci: npcm: Initialize state before requesting IRQ

 drivers/peci/controller/peci-aspeed.c | 8 ++++----
 drivers/peci/controller/peci-npcm.c   | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)

                 reply	other threads:[~2026-09-25 21:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=14b83bcafac21987132c08a23043254c6c43e3ec.camel@intel.com \
    --to=iwona.winiarska@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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®