linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>,
	ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Olof Johansson <olof@lixom.net>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>
Subject: [GIT PULL] firmware: arm_scmi: fix for v5.5
Date: Mon, 2 Dec 2019 11:45:59 +0000	[thread overview]
Message-ID: <20191202114559.GB20965@bogus> (raw)

Hi ARM SoC Team,

Please pull !

Regards,
Sudeep

-->8

The following changes since commit 7bd39bc6bfdf96f5df0f92199bbc1a3ee2f2adb8:

  firmware: arm_scmi: Fix doorbell ring logic for !CONFIG_64BIT (2019-11-14 11:13:50 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/scmi-fix-5.5-2

for you to fetch changes up to 8305e90a894f82c278c17e51a28459deee78b263:

  firmware: arm_scmi: Avoid double free in error flow (2019-11-26 10:50:30 +0000)

----------------------------------------------------------------
ARM SCMI fix for v5.5

Yet another single fix to avoid double freeing in scmi_device_create
error path

----------------------------------------------------------------
Wen Yang (1):
      firmware: arm_scmi: Avoid double free in error flow

 drivers/firmware/arm_scmi/bus.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-12-02 11:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 11:45 Sudeep Holla [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-13 18:04 [GIT PULL] firmware: arm_scmi: fix for v5.5 Sudeep Holla

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=20191202114559.GB20965@bogus \
    --to=sudeep.holla@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).