Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1563266 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-01-20 04:30 +0100 |
| Last post | 2017-01-20 14:30 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
linux-next: manual merge of the scsi tree with the tip tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-20 04:30 +0100
Re: linux-next: manual merge of the scsi tree with the tip tree Ingo Molnar <mingo@kernel.org> - 2017-01-20 07:50 +0100
Re: linux-next: manual merge of the scsi tree with the tip tree James Bottomley <James.Bottomley@HansenPartnership.com> - 2017-01-20 14:00 +0100
Re: linux-next: manual merge of the scsi tree with the tip tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-20 14:30 +0100
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-01-20 04:30 +0100 |
| Subject | linux-next: manual merge of the scsi tree with the tip tree |
| Message-ID | <t1y3L-1Vd-5@gated-at.bofh.it> |
Hi James,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/mpt3sas/mpt3sas_scsih.c
between commit:
e963b7088dac ("scsi: mpt3sas: Fix hang on ata passthru commands")
from the tip tree and commit:
ffb584565894 ("scsi: mpt3sas: fix hang on ata passthrough commands")
from the scsi tree.
I fixed it up (slightly different versions of the same patch - I 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
[toc] | [next] | [standalone]
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Date | 2017-01-20 07:50 +0100 |
| Message-ID | <t1Bbk-3QV-3@gated-at.bofh.it> |
| In reply to | #1563266 |
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi James,
>
> Today's linux-next merge of the scsi tree got a conflict in:
>
> drivers/scsi/mpt3sas/mpt3sas_scsih.c
>
> between commit:
>
> e963b7088dac ("scsi: mpt3sas: Fix hang on ata passthru commands")
>
> from the tip tree and commit:
>
> ffb584565894 ("scsi: mpt3sas: fix hang on ata passthrough commands")
>
> from the scsi tree.
>
> I fixed it up (slightly different versions of the same patch - I 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.
I only had that patch for testing and it went into the -next branch by accident -
I have removed it so the conflict should be gone next time -next is integrated.
Thanks,
Ingo
[toc] | [prev] | [next] | [standalone]
| From | James Bottomley <James.Bottomley@HansenPartnership.com> |
|---|---|
| Date | 2017-01-20 14:00 +0100 |
| Message-ID | <t1GXn-7lE-1@gated-at.bofh.it> |
| In reply to | #1563322 |
On Fri, 2017-01-20 at 07:35 +0100, Ingo Molnar wrote:
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi James,
> >
> > Today's linux-next merge of the scsi tree got a conflict in:
> >
> > drivers/scsi/mpt3sas/mpt3sas_scsih.c
> >
> > between commit:
> >
> > e963b7088dac ("scsi: mpt3sas: Fix hang on ata passthru commands")
> >
> > from the tip tree and commit:
> >
> > ffb584565894 ("scsi: mpt3sas: fix hang on ata passthrough
> > commands")
> >
> > from the scsi tree.
> >
> > I fixed it up (slightly different versions of the same patch - I
> > 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 or merging. You may also want to consider
> > cooperating with the maintainer of the conflicting tree to minimise
> > any particularly complex conflicts.
>
> I only had that patch for testing and it went into the -next branch
> by accident - I have removed it so the conflict should be gone next
> time -next is integrated.
Thanks for testing. There was a last minute fuss about whether the
flag should be checked using a test_bit rather than a straight read,
which is the difference between the two versions.
James
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-01-20 14:30 +0100 |
| Message-ID | <t1Hqq-7M4-15@gated-at.bofh.it> |
| In reply to | #1563322 |
Hi Ingo, On Fri, 20 Jan 2017 07:35:52 +0100 Ingo Molnar <mingo@kernel.org> wrote: > > I only had that patch for testing and it went into the -next branch by accident - > I have removed it so the conflict should be gone next time -next is integrated. Thanks, these things happen. -- Cheers, Stephen Rothwell
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web