From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
"Nicholas A. Bellinger" <nab@daterainc.com>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sagi Grimberg <sagig@mellanox.com>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH-v2 0/6] vhost/scsi: Add T10 PI SGL passthrough support
Date: Tue, 10 Jun 2014 16:02:08 +0300 [thread overview]
Message-ID: <20140610130208.GA27702@redhat.com> (raw)
In-Reply-To: <20140610215217.495d5476@canb.auug.org.au>
On Tue, Jun 10, 2014 at 09:52:17PM +1000, Stephen Rothwell wrote:
> Hi Michael,
>
> On Tue, 10 Jun 2014 12:42:54 +0300 "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >
> > So I see two options:
> > - I go ahead with my changes and you with yours and let Linus resolve
> > the conflict. This means bisect build will be broken since the
> > breakage will likely not be noticed until after the merge.
>
> Well, since the resolution is known, the one who submits their tree
> later should tell Linus (as suggested by Nicholas). That is part of
> the point of the linux-next tree ... and therefore there would be no
> bisect problem.
>
> > > Stephen (CC'ed) has included a fix in today's linux-next for the merge
> > > conflict here:
> > >
> > > https://lkml.org/lkml/2014/6/10/3
> > >
> > > Please confirm, as it will be a pointer to Linus within the
> > > target-pending/for-next PULL request.
> >
> > Yes but this does mean people trying to bisect will
> > hit build breakages, not nice.
>
> Not necessarily.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
I don't see how that's possible.
Here's a point you might have missed.
Nicholas's patch isn't just introducing a merge conflict.
It is also buggy.
Replacing bit access with has_feature silently fixes the bug.
So if we want to avoid bisect breakage target tree will
have to be rebased.
And if doing that anyway, I don't see any reason not
to merge everything through the vhost tree, esp
since I already put the patches there. Less work for
everyone involved.
--
MST
next prev parent reply other threads:[~2014-06-10 13:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 2:26 [PATCH-v2 0/6] vhost/scsi: Add T10 PI SGL passthrough support Nicholas A. Bellinger
2014-05-22 2:26 ` [PATCH-v2 1/6] virtio-scsi.h: Add virtio_scsi_cmd_req_pi + VIRTIO_SCSI_F_T10_PI bits Nicholas A. Bellinger
2014-05-22 6:57 ` Michael S. Tsirkin
2014-05-22 11:00 ` Rusty Russell
2014-05-22 20:38 ` Nicholas A. Bellinger
2014-06-09 13:16 ` Michael S. Tsirkin
2014-05-22 2:26 ` [PATCH-v2 2/6] vhost/scsi: Move sanity check into vhost_scsi_map_iov_to_sgl Nicholas A. Bellinger
2014-05-22 2:26 ` [PATCH-v2 3/6] vhost/scsi: Add preallocation of protection SGLs Nicholas A. Bellinger
2014-05-22 2:26 ` [PATCH-v2 4/6] vhost/scsi: Add T10 PI IOV -> SGL memory mapping logic Nicholas A. Bellinger
2014-05-22 2:26 ` [PATCH-v2 5/6] vhost/scsi: Enable T10 PI IOV -> SGL memory mapping Nicholas A. Bellinger
2014-06-09 13:15 ` Michael S. Tsirkin
2014-05-22 2:26 ` [PATCH-v2 6/6] virtio-scsi: Enable DIF/DIX modes in SCSI host LLD Nicholas A. Bellinger
2014-05-22 8:37 ` Paolo Bonzini
2014-05-22 20:41 ` Nicholas A. Bellinger
2014-05-22 8:37 ` [PATCH-v2 0/6] vhost/scsi: Add T10 PI SGL passthrough support Paolo Bonzini
2014-06-02 7:31 ` Michael S. Tsirkin
2014-06-08 16:05 ` Michael S. Tsirkin
2014-06-09 9:06 ` Paolo Bonzini
2014-06-10 7:07 ` Nicholas A. Bellinger
2014-06-10 8:03 ` Paolo Bonzini
2014-06-09 13:30 ` Michael S. Tsirkin
2014-06-10 7:05 ` Nicholas A. Bellinger
2014-06-10 9:42 ` Michael S. Tsirkin
2014-06-10 11:52 ` Stephen Rothwell
2014-06-10 13:02 ` Michael S. Tsirkin [this message]
2014-06-10 15:47 ` Stephen Rothwell
2014-06-10 17:39 ` Nicholas A. Bellinger
2014-06-10 18:45 ` Michael S. Tsirkin
2014-06-10 19:57 ` Nicholas A. Bellinger
2014-06-10 20:09 ` James Bottomley
2014-06-10 20:25 ` Nicholas A. Bellinger
2014-06-10 20:56 ` Linus Torvalds
2014-06-10 21:20 ` Nicholas A. Bellinger
2014-06-11 8:04 ` Michael S. Tsirkin
2014-06-10 19:35 ` Michael S. Tsirkin
2014-06-10 19:53 ` Nicholas A. Bellinger
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=20140610130208.GA27702@redhat.com \
--to=mst@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nab@daterainc.com \
--cc=nab@linux-iscsi.org \
--cc=pbonzini@redhat.com \
--cc=sagig@mellanox.com \
--cc=sfr@canb.auug.org.au \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).