From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Rob Herring <robh@kernel.org>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [linux-next:master 2607/4710] drivers/gpio/gpio-ge.c:59:32: error: invalid use of undefined type 'struct platform_device'
Date: Wed, 26 Jul 2023 20:42:08 +0300 [thread overview]
Message-ID: <CAHp75VfEbHkNGCSy1QVVC20STgTXZ7KkYhDcHj_OK0yPPAZU0Q@mail.gmail.com> (raw)
In-Reply-To: <202307270116.Xf7g8Lne-lkp@intel.com>
On Wed, Jul 26, 2023 at 8:24 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 0ba5d07205771c50789fd9063950aa75e7f1183f
> commit: e91d0f05e66afba9a3804bccf3d0a4310bb30024 [2607/4710] gpio: Explicitly include correct DT includes
> config: powerpc-randconfig-r036-20230726 (https://download.01.org/0day-ci/archive/20230727/202307270116.Xf7g8Lne-lkp@intel.com/config)
> compiler: powerpc-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230727/202307270116.Xf7g8Lne-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307270116.Xf7g8Lne-lkp@intel.com/
>
> All error/warnings (new ones prefixed by >>):
>
The series
https://lore.kernel.org/linux-gpio/20230724161320.63876-1-andriy.shevchenko@linux.intel.com/
fixes in particular this issue(s).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-07-26 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 17:24 kernel test robot
2023-07-26 17:42 ` Andy Shevchenko [this message]
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=CAHp75VfEbHkNGCSy1QVVC20STgTXZ7KkYhDcHj_OK0yPPAZU0Q@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
/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