mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.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>,
	"Martin K. Petersen" <mkp@kernel.org>
Subject: Re: linux-next: manual merge of the scsi-mkp tree with the origin tree
Date: Fri, 18 Sep 2026 07:12:21 +0200	[thread overview]
Message-ID: <aqzINeKnw7kCQzxw@ryzen> (raw)
In-Reply-To: <aqxB2gIACLhW5I0-@sirena.org.uk>

On Thu, Sep 17, 2026 at 08:39:06PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the scsi-mkp tree got a conflict in:
> 
>   drivers/ata/libata-scsi.c
> 
> between commit:
> 
>   6d81700ad7c48 ("ata: libata-scsi: do not raise UA for storage element depopulation and restoration")
> 
> from the origin tree and commit:
> 
>   c44f095a9d176 ("scsi: ata: libata: Use combined sense codes")
> 
> from the scsi-mkp tree.
> 
> 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.

Mark, thank you for the notice.

Martin, as Damien mentioned in the cover letter:
https://lore.kernel.org/linux-scsi/20260908090308.1085097-1-dlemoal@kernel.org/T/#mcf890a9a7d47f717b6362a76c8fb8760a58d7761

Perhaps you could either:
-Rebase scsi-staging on top of -rc2
or
-Merge in -rc2 to scsi-staging


Kind regards,
Niklas

  reply	other threads:[~2026-09-18  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 19:39 Mark Brown
2026-09-18  5:12 ` Niklas Cassel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-17 20:09 Mark Brown
2026-07-13 15:13 Mark Brown
2026-07-16 10:13 ` Uwe Kleine-König
2026-07-16 13:03   ` Mark Brown
2026-07-16 13:09     ` Martin K. Petersen
2026-07-16 13:20       ` Mark Brown
2026-03-30 19:58 Mark Brown

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=aqzINeKnw7kCQzxw@ryzen \
    --to=cassel@kernel.org \
    --cc=broonie@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mkp@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

all inboxes | Powered by JetHome®