All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: gregkh@linuxfoundation.org
Cc: yilun.xu@intel.com, linux-fpga@vger.kernel.org, hao.wu@intel.com,
	mdf@kernel.org
Subject: [GIT PULL] FPGA Manager changes for 6.2 final
Date: Sat, 28 Jan 2023 22:42:20 +0800	[thread overview]
Message-ID: <Y9U0TASyMnHzbDtp@yilunxu-OptiPlex-7050> (raw)

The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:

  Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/fpga/linux-fpga tags/fpga-for-6.2-final

for you to fetch changes up to 60ce26d10e5850f33cc76fce52f5377045e75a15:

  fpga: m10bmc-sec: Fix probe rollback (2022-12-30 10:49:52 +0800)

----------------------------------------------------------------
FPGA Manager changes for 6.2-final

stratix10-soc:

- Zheng's change fixes return value check

Intel m10 bmc secure update:

- Ilpo's change fixes probe rollback

All patches have been reviewed on the mailing list, and have been in the
last linux-next releases (as part of our for-6.2 branch)

Signed-off-by: Xu Yilun <yilun.xu@intel.com>

----------------------------------------------------------------
Ilpo Järvinen (1):
      fpga: m10bmc-sec: Fix probe rollback

Zheng Yongjun (1):
      fpga: stratix10-soc: Fix return value check in s10_ops_write_init()

 drivers/fpga/intel-m10-bmc-sec-update.c | 17 ++++++++++++-----
 drivers/fpga/stratix10-soc.c            |  4 ++--
 2 files changed, 14 insertions(+), 7 deletions(-)

             reply	other threads:[~2023-01-28 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 14:42 Xu Yilun [this message]
2023-01-28 18:20 ` [GIT PULL] FPGA Manager changes for 6.2 final Greg KH

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=Y9U0TASyMnHzbDtp@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@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 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.