From: Damien Le Moal <damien.lemoal@opensource•wdc.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patches in the libata tree
Date: Tue, 3 Oct 2023 09:35:58 +0900 [thread overview]
Message-ID: <b18388fd-ff86-14cb-45f7-6eb56e4bb60e@opensource.wdc.com> (raw)
In-Reply-To: <20231003080744.69ca4ed0@canb.auug.org.au>
On 10/3/23 06:07, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 0e23330fccd4 ("ata: libata-scsi: Disable scsi device manage_system_start_stop")
> 1cf14228f460 ("scsi: sd: Differentiate system and runtime start/stop management")
> 540bd522a82e ("ata: libata-scsi: link ata port and scsi device")
> 54e5c956a103 ("scsi: sd: Do not issue commands to suspended disks on shutdown")
> 6d62f34a6741 ("ata: libata-core: Fix ata_port_request_pm() locking")
> 7c412cfbeecf ("scsi: Do not attempt to rescan suspended devices")
> 9459518aba7b ("ata: libata-scsi: Fix delayed scsi_rescan_device() execution")
> cb37013b985e ("ata: libata-eh: Fix compilation warning in ata_eh_link_report()")
> e4bfeedb3b50 ("ata: libata-core: Fix port and device removal")
> f215cc816f8f ("ata: libata-core: Do not register PM operations for SAS ports")
> fdd57890e769 ("ata: libata-core: Fix compilation warning in ata_dev_config_ncq()")
>
Stephen,
Sorry about that. Will fix this asap.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-10-03 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 21:07 linux-next: duplicate patches in the libata tree Stephen Rothwell
2023-10-03 0:35 ` Damien Le Moal [this message]
2023-10-03 0:46 ` Damien Le Moal
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=b18388fd-ff86-14cb-45f7-6eb56e4bb60e@opensource.wdc.com \
--to=damien.lemoal@opensource$(echo .)wdc.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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