From: Shuah Khan <shuahkh@osg.samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"bamvor.zhangjian@huawei.com" <bamvor.zhangjian@huawei.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Shuah Khan" <shuahkh@osg.samsung.com>
Subject: Re: linux-next: manual merge of the kselftest tree with the net-next tree
Date: Wed, 22 Feb 2017 07:54:21 -0700 [thread overview]
Message-ID: <a7dfa6bf-1bcb-aa44-4099-a86caf5f1f5a@osg.samsung.com> (raw)
In-Reply-To: <20170216142453.53d1f5e5@canb.auug.org.au>
On 02/15/2017 08:24 PM, Stephen Rothwell wrote:
> Hi Shuah,
>
> Today's linux-next merge of the kselftest tree got a conflict in:
>
> tools/testing/selftests/bpf/Makefile
>
> between commit:
>
> d498f8719a09 ("bpf: Rebuild bpf.o for any dependency update")
>
> from the net-next tree and commit:
>
> 88baa78d1f31 ("selftests: remove duplicated all and clean target")
>
> from the kselftest 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.
>
Sorry to get back to you late. I was away on vacation last week.
Yes. Please let's plan upon carrying the fix.
thanks,
-- Shuah
next prev parent reply other threads:[~2017-02-22 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 3:24 linux-next: manual merge of the kselftest tree with the net-next tree Stephen Rothwell
2017-02-22 14:54 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 4:03 Stephen Rothwell
2017-01-25 7:39 ` Daniel Borkmann
2017-01-24 4:45 Stephen Rothwell
2017-01-24 15:17 ` Shuah Khan
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=a7dfa6bf-1bcb-aa44-4099-a86caf5f1f5a@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=bamvor.zhangjian@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mic@digikod.net \
--cc=netdev@vger.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 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).