From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Networking <netdev@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
David Miller <davem@davemloft.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alex Shi <alex.shi@linux.alibaba.com>
Subject: Re: linux-next: manual merge of the bpf-next tree with the jc_docs tree
Date: Mon, 15 Apr 2019 11:09:02 +1000 [thread overview]
Message-ID: <20190415110902.41c3c201@canb.auug.org.au> (raw)
In-Reply-To: <20190412110518.46e329af@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
Hi all,
On Fri, 12 Apr 2019 11:05:18 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> .mailmap
>
> between commit:
>
> 9b628c6ab437 ("mailmap: update my obsolete email address")
>
> from the jc_docs tree and commit:
>
> fa0dcb3fe2ca ("mailmap: add entry for email addresses")
>
> from the bpf-next 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.
>
> diff --cc .mailmap
> index 151501c73503,e7984bb6b4b0..000000000000
> --- a/.mailmap
> +++ b/.mailmap
> @@@ -16,8 -16,9 +16,11 @@@ Alan Cox <alan@lxorguk.ukuu.org.uk
> Alan Cox <root@hraefn.swansea.linux.org.uk>
> Aleksey Gorelov <aleksey_gorelov@phoenix.com>
> Aleksandar Markovic <aleksandar.markovic@mips.com> <aleksandar.markovic@imgtec.com>
> +Alex Shi <alex.shi@linux.alibaba.com> <alex.shi@intel.com>
> +Alex Shi <alex.shi@linux.alibaba.com> <alex.shi@linaro.org>
> + Alexei Starovoitov <ast@kernel.org> <ast@plumgrid.com>
> + Alexei Starovoitov <ast@kernel.org> <alexei.starovoitov@gmail.com>
> + Alexei Starovoitov <ast@kernel.org> <ast@fb.com>
> Al Viro <viro@ftp.linux.org.uk>
> Al Viro <viro@zenIV.linux.org.uk>
> Andi Shyti <andi@etezian.org> <andi.shyti@samsung.com>
This is now a conflict between the net-next tree and the jc_docs tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-15 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:05 linux-next: manual merge of the bpf-next tree with the jc_docs tree Stephen Rothwell
2019-04-15 1:09 ` Stephen Rothwell [this message]
[not found] ` <a01e1602-3e82-f118-5fe4-1572647c06f9@linux.alibaba.com>
2019-04-15 13:45 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2020-03-13 2:58 Stephen Rothwell
2020-03-13 19:51 ` Alexei Starovoitov
2020-03-13 20:08 ` Stephen Kitt
2021-11-17 23:13 Stephen Rothwell
2021-11-17 23:20 ` Daniel Borkmann
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=20190415110902.41c3c201@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.shi@linux.alibaba.com \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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