Content-Type: multipart/mixed; boundary="===============0474536113022556754==" MIME-Version: 1.0 From: Philip Li To: kbuild-all@lists.01.org Subject: Re: [PATCH v3 1/3] pinctrl: intel: Make use of for_each_requested_gpio_in_range() Date: Wed, 17 Jun 2020 09:14:29 +0800 Message-ID: <20200617011429.GB29542@intel.com> In-Reply-To: List-Id: --===============0474536113022556754== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Jun 16, 2020 at 08:36:11AM +0300, Andy Shevchenko wrote: > On Tue, Jun 16, 2020 at 4:18 AM kernel test robot wrote: > > > > Hi Andy, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on pinctrl/devel] > > [also build test ERROR on v5.8-rc1 next-20200615] > > [if your patch is applied to the wrong git tree, please drop us a note = to help > > improve the system. BTW, we also suggest to use '--base' option to spec= ify the > > base tree in git format-patch, please see https://stackoverflow.com/a/3= 7406982] > = > Is there a way to tell kbuild bot to use another patch series (by link > to lore?) that should be used as a base? Hi Andy, currently we recommend to use --base option to deduce the base com= mit, and bot will read this information to find a better tree as base that conta= ins the base commit. > In any case this series has such links in a cover letter. Can kbuild > bot parse it (perhaps some special tag, like BaseLink: is needed)? We haven't support other way yet. With --base option, we will parse the extra information added by --base. > = > = > -- = > With Best Regards, > Andy Shevchenko > _______________________________________________ > kbuild-all mailing list -- kbuild-all(a)lists.01.org > To unsubscribe send an email to kbuild-all-leave(a)lists.01.org --===============0474536113022556754==--