From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jonathan Corbet <corbet@lwn•net>, Bjorn Helgaas <bhelgaas@google•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Logan Gunthorpe <logang@deltatee•com>,
Randy Dunlap <rdunlap@infradead•org>
Subject: linux-next: manual merge of the jc_docs tree with the pci tree
Date: Tue, 16 Oct 2018 09:56:12 +1100 [thread overview]
Message-ID: <20181016095612.36b5e7bb@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
Hi Jonathan,
Today's linux-next merge of the jc_docs tree got a conflict in:
Documentation/driver-api/index.rst
between commit:
7618a41f1a25 ("docs-rst: Add a new directory for PCI documentation")
from the pci tree and commit:
ea2ae0ecc9ad ("FireWire: add a Documentation driver-api chapter")
from the jc_docs 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/driver-api/index.rst
index e9e7d24169cf,1f0cdba2b2bf..000000000000
--- a/Documentation/driver-api/index.rst
+++ b/Documentation/driver-api/index.rst
@@@ -29,7 -29,8 +29,8 @@@ available subsections can be seen below
iio/index
input
usb/index
+ firewire
- pci
+ pci/index
spi
i2c
hsi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2018-10-15 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181016095612.36b5e7bb@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bhelgaas@google$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=logang@deltatee$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
/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