From: Philip Li <philip.li@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
kbuild-all@lists.01.org
Subject: Re: [kbuild-all] 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 [thread overview]
Message-ID: <20200617011429.GB29542@intel.com> (raw)
In-Reply-To: <CAHp75VfnNAUUK1nUyJbBEQxYLp5zc1pC8ASjg8DtOfGtrk7DVg@mail.gmail.com>
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 <lkp@intel.com> 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 specify the
> > base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> 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 commit,
and bot will read this information to find a better tree as base that contains
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@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
next prev parent reply other threads:[~2020-06-17 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 15:13 [PATCH v3 0/3] pinctrl: intel: Reuse for_each_requested_gpio*() macros Andy Shevchenko
2020-06-15 15:13 ` [PATCH v3 1/3] pinctrl: intel: Make use of for_each_requested_gpio_in_range() Andy Shevchenko
2020-06-16 1:16 ` kernel test robot
2020-06-16 5:36 ` Andy Shevchenko
2020-06-17 1:14 ` Philip Li [this message]
2020-06-15 15:13 ` [PATCH v3 2/3] pinctrl: lynxpoint: Make use of for_each_requested_gpio() Andy Shevchenko
2020-06-16 3:42 ` kernel test robot
2020-06-15 15:13 ` [PATCH v3 3/3] pinctrl: lynxpoint: Introduce helpers to enable or disable input Andy Shevchenko
2020-06-15 16:33 ` [PATCH v3 0/3] pinctrl: intel: Reuse for_each_requested_gpio*() macros Mika Westerberg
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=20200617011429.GB29542@intel.com \
--to=philip.li@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.com \
/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).