From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v1 1/1] pinctrl: core: Drop unused include
Date: Sat, 21 Mar 2026 15:19:24 +0200 [thread overview]
Message-ID: <ab6a3MACb9fed99h@ashevche-desk.local> (raw)
In-Reply-To: <202603211748.5YfMNVO3-lkp@intel.com>
On Sat, Mar 21, 2026 at 05:55:35PM +0800, kernel test robot wrote:
> Hi Andy,
>
> kernel test robot noticed the following build errors:
Ouch!
So, seems the gpio.h is used as a 'proxy' for some other headers.
I will test it carefully before sending v2.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-03-21 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 22:05 [PATCH v1 1/1] pinctrl: core: Drop unused include Andy Shevchenko
2026-03-21 7:27 ` kernel test robot
2026-03-21 9:55 ` kernel test robot
2026-03-21 9:55 ` kernel test robot
2026-03-21 13:19 ` Andy Shevchenko [this message]
2026-03-23 13:30 ` Linus Walleij
2026-03-23 13:36 ` 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=ab6a3MACb9fed99h@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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