All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ide@vger.kernel.org
Subject: [GIT PULL] libata fixes for 5.16-rc4
Date: Fri,  3 Dec 2021 19:40:33 +0900	[thread overview]
Message-ID: <20211203104033.656678-1-damien.lemoal@opensource.wdc.com> (raw)

Linus,

The following changes since commit d58071a8a76d779eedab38033ae4c821c30295a5:

  Linux 5.16-rc3 (2021-11-28 14:09:19 -0800)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata tags/libata-5.16-rc4

for you to fetch changes up to 06d5d558f5a30582546dcbe9327601af867ce1c9:

  ata: replace snprintf in show functions with sysfs_emit (2021-12-02 13:13:45 +0900)

----------------------------------------------------------------
libata fixes for 5.16-rc4

Two sparse warning fixes and a couple of patches to fix an issue with
sata_fsl driver module removal:

* A couple of patches to avoid sparse warnings in libata-sata and
  in the pata_falcon driver (from Yang and Finn).
* A couple of sata_fsl driver patches fixing IRQ free and proc
  unregister on module removal (from Baokun).
----------------------------------------------------------------

Baokun Li (2):
      sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
      sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl

Finn Thain (1):
      pata_falcon: Avoid type warnings from sparse

Yang Guang (1):
      ata: replace snprintf in show functions with sysfs_emit

 drivers/ata/libata-sata.c |  2 +-
 drivers/ata/pata_falcon.c | 16 ++++++++--------
 drivers/ata/sata_fsl.c    | 20 +++++++++++++-------
 3 files changed, 22 insertions(+), 16 deletions(-)

             reply	other threads:[~2021-12-03 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 10:40 Damien Le Moal [this message]
2021-12-03 18:53 ` [GIT PULL] libata fixes for 5.16-rc4 pr-tracker-bot

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=20211203104033.656678-1-damien.lemoal@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.