From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kernel test robot <yujie.liu@intel.com>,
Raag Jadav <raag.jadav@intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
oe-kbuild-all@lists.linux.dev,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 2/2] pinctrl: intel: Add a generic Intel pin control platform driver
Date: Tue, 14 Nov 2023 13:50:24 +0200 [thread overview]
Message-ID: <20231114115024.GV17433@black.fi.intel.com> (raw)
In-Reply-To: <ZVNczZMruhh59Vfc@smile.fi.intel.com>
On Tue, Nov 14, 2023 at 01:41:01PM +0200, Andy Shevchenko wrote:
> On Tue, Nov 14, 2023 at 09:46:07AM +0800, kernel test robot wrote:
> > Hi Andy,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on linusw-pinctrl/devel]
> > [also build test ERROR on linusw-pinctrl/for-next linus/master v6.7-rc1 next-20231113]
>
> False positive as the dependencies appeared in today's Linux Next.
>
> $ git tag --contains 22f57707fa0c
> next-20231114
Okay thanks for checking!
The series looks good to me so feel free to add,
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2023-11-14 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 12:28 [PATCH v2 0/2] pinctrl: intel: Add generic platform driver Andy Shevchenko
2023-11-13 12:28 ` [PATCH v2 1/2] pinctrl: intel: Revert "Unexport intel_pinctrl_probe()" Andy Shevchenko
2023-11-13 12:28 ` [PATCH v2 2/2] pinctrl: intel: Add a generic Intel pin control platform driver Andy Shevchenko
2023-11-14 1:46 ` kernel test robot
2023-11-14 11:41 ` Andy Shevchenko
2023-11-14 11:50 ` Mika Westerberg [this message]
2023-11-14 12:11 ` Andy Shevchenko
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=20231114115024.GV17433@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raag.jadav@intel.com \
--cc=yujie.liu@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