From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Changbin Du <changbin.du@gmail.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Subject: Re: linux-next: manual merge of the usb tree with the pci tree
Date: Tue, 9 Jul 2019 08:35:10 +0200 [thread overview]
Message-ID: <20190709063510.GB10587@kroah.com> (raw)
In-Reply-To: <20190709095833.727ac5e8@canb.auug.org.au>
On Tue, Jul 09, 2019 at 09:58:33AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 24 Jun 2019 17:47:29 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the usb tree got a conflict in:
> >
> > Documentation/index.rst
> >
> > between commit:
> >
> > c42eaffa1656 ("Documentation: add Linux PCI to Sphinx TOC tree")
> >
> > from the pci tree and commit:
> >
> > ecefae6db042 ("docs: usb: rename files to .rst and add them to drivers-api")
> >
> > from the usb 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.
> >
> > --
> > Cheers,
> > Stephen Rothwell
> >
> > diff --cc Documentation/index.rst
> > index 239100accbf6,91055adde327..000000000000
> > --- a/Documentation/index.rst
> > +++ b/Documentation/index.rst
> > @@@ -101,7 -101,7 +101,8 @@@ needed)
> > filesystems/index
> > vm/index
> > bpf/index
> > + PCI/index
> > + usb/index
> > misc-devices/index
> >
> > Architecture-specific documentation
>
> I am still getting this conflict (the commit ids may have changed).
> Just a reminder in case you think Linus may need to know.
For a merge issue like this, I think he can handle it :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-09 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:12 linux-next: manual merge of the usb tree with the pci tree Stephen Rothwell
2019-06-24 7:34 ` Greg KH
2019-06-24 7:47 ` Stephen Rothwell
2019-07-08 23:58 ` Stephen Rothwell
2019-07-09 6:35 ` Greg KH [this message]
2019-07-09 6:53 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-09-21 5:18 Stephen Rothwell
2020-09-21 15:50 ` Greg KH
2020-10-15 21:47 ` Stephen Rothwell
2020-10-16 7:26 ` Jim Quinlan
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=20190709063510.GB10587@kroah.com \
--to=greg@kroah.com \
--cc=bhelgaas@google.com \
--cc=changbin.du@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.