linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: 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: [PATCH v3 1/3] pinctrl: intel: Make use of for_each_requested_gpio_in_range()
Date: Tue, 16 Jun 2020 08:36:11 +0300	[thread overview]
Message-ID: <CAHp75VfnNAUUK1nUyJbBEQxYLp5zc1pC8ASjg8DtOfGtrk7DVg@mail.gmail.com> (raw)
In-Reply-To: <202006160949.aOLXxFhV%lkp@intel.com>

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?
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)?


-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2020-06-16  5:36 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 [this message]
2020-06-17  1:14       ` [kbuild-all] " Philip Li
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=CAHp75VfnNAUUK1nUyJbBEQxYLp5zc1pC8ASjg8DtOfGtrk7DVg@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=andriy.shevchenko@linux.intel.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).