public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Damien Le Moal <dlemoal@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the libata tree with the origin tree
Date: Mon, 9 Mar 2026 17:56:37 +0100	[thread overview]
Message-ID: <aa77xS2TewAwB3_N@ryzen> (raw)
In-Reply-To: <aa7uBn7h20yFEUF4@sirena.org.uk>

On Mon, Mar 09, 2026 at 03:57:58PM +0000, Mark Brown wrote:

(snip)

> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> diff --cc drivers/ata/libata-scsi.c
> index ad798e5246b49,4225c6d7ff359..0000000000000
> --- a/drivers/ata/libata-scsi.c
> +++ b/drivers/ata/libata-scsi.c
> @@@ -1694,15 -1697,10 +1697,11 @@@ void ata_scsi_requeue_deferred_qc(struc
>   	 * do not try to be smart about what to do with this deferred command
>   	 * and simply retry it by completing it with DID_SOFT_ERROR.
>   	 */
> - 	if (!qc)
> - 		return;
> - 
> - 	scmd = qc->scsicmd;
> - 	ap->deferred_qc = NULL;
> - 	cancel_work(&ap->deferred_qc_work);
> - 	ata_qc_free(qc);
> - 	scmd->result = (DID_SOFT_ERROR << 16);
> - 	scsi_done(scmd);
> + 	if (qc) {
> + 		ap->deferred_qc = NULL;
> ++		cancel_work(&ap->deferred_qc_work);
> + 		ata_scsi_qc_done(qc, true, DID_SOFT_ERROR << 16);
> + 	}
>   }
>   
>   static void ata_scsi_schedule_deferred_qc(struct ata_port *ap)

Hello Mark,

Your conflict resolution looks correct.

I decided to merge for-7.0-fixes branch into for-7.1 / for-next,
for simplicity.

This way, no need to bother Linus with a conflict resolution once
the merge window opens.

Thank you for the heads-up!


Kind regards,
Niklas

      reply	other threads:[~2026-03-09 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 15:57 linux-next: manual merge of the libata tree with the origin tree Mark Brown
2026-03-09 16:56 ` Niklas Cassel [this message]

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=aa77xS2TewAwB3_N@ryzen \
    --to=cassel@kernel.org \
    --cc=broonie@kernel.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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