From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle•com>,
James Bottomley <James.Bottomley@HansenPartnership•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Darren Trapp <darren.trapp@cavium•com>,
Himanshu Madhani <himanshu.madhani@cavium•com>
Subject: linux-next: manual merge of the scsi-mkp tree with the scsi tree
Date: Fri, 26 Jan 2018 09:39:14 +1100 [thread overview]
Message-ID: <20180126093914.4afaed4c@canb.auug.org.au> (raw)
Hi Martin,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/qla2xxx/qla_init.c
between commit:
07a21872cf2b ("scsi: qla2xxx: Fix queue ID for async abort with Multiqueue")
from the scsi tree and commit:
b027a5ace443 ("scsi: qla2xxx: Fix queue ID for async abort with Multiqueue")
from the scsi-mkp tree.
Looks like you have updated your tree after James has merged it :-(
I fixed it up (I just used the latter version) 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.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2018-01-25 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 22:39 Stephen Rothwell [this message]
2018-01-25 23:18 ` linux-next: manual merge of the scsi-mkp tree with the scsi tree James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 6:40 Stephen Rothwell
2016-11-09 2:57 Stephen Rothwell
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=20180126093914.4afaed4c@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=darren.trapp@cavium$(echo .)com \
--cc=himanshu.madhani@cavium$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
/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