[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170426061403.GI29367@yexl-desktop>
Date: Wed, 26 Apr 2017 14:14:03 +0800
From: Ye Xiaolong <xiaolong.ye@...el.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: kbuild test robot <lkp@...el.com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-block@...r.kernel.org, dm-devel@...hat.com,
kbuild-all@...org, linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Gerald Schaefer <gerald.schaefer@...ibm.com>
Subject: Re: [kbuild-all] [PATCH v3] axon_ram: add dax_operations support
On 04/19, Dan Williams wrote:
>On Wed, Apr 19, 2017 at 8:01 PM, kbuild test robot <lkp@...el.com> wrote:
>> Hi Dan,
>>
>> [auto build test ERROR on powerpc/next]
>> [also build test ERROR on v4.11-rc7 next-20170419]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>
>>
>> url: https://github.com/0day-ci/linux/commits/Dan-Williams/axon_ram-add-dax_operations-support/20170420-091615
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
>
>Hi kbuild team, yes this is the wrong base. It's part of a larger
>series [1] and I'm just re-sending a few select patches with updates
>from review, rather than the full 33 patch series. Any better way to
>send individual updates to a patch in a series without re-sending the
>whole series?
Thanks for the feedback, as it's a common practice in community, we are
developing a new feature to recognize the updated patch of a patch series, and
apply it together with the whole patchset other than applying it individually.
Thanks,
Xiaolong
>
>[1]: https://lkml.org/lkml/2017/4/14/495
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@...ts.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all
Powered by blists - more mailing lists