[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2E9CBF79-3075-48FF-87D8-834DCE1E5D9D@fb.com>
Date: Wed, 2 May 2018 06:05:46 +0000
From: Song Liu <songliubraving@...com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Networking <netdev@...r.kernel.org>,
"Linux-Next Mailing List" <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yonghong Song <yhs@...com>
Subject: Re: linux-next: manual merge of the bpf-next tree with the bpf tree
> On May 1, 2018, at 10:50 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Song,
>
> On Wed, 2 May 2018 04:40:20 +0000 Song Liu <songliubraving@...com> wrote:
>>
>>> - CHECK(build_id_matches < 1, "build id match",
>>> - "Didn't find expected build ID from the map\n");
>>> + if (CHECK(build_id_matches < 1, "build id match",
>>> - "Didn't find expected build ID from the map"))
>>> ++ "Didn't find expected build ID from the map\n"))
>>
>> ^^^ Is there a "+" at the beginning of this line?
>
> No, this is a merge resolution diff, so the ++ means that the line did
> not appear in either parent commit.
Hi Stephen,
Thanks for the explanation!
Song
Powered by blists - more mailing lists