From: Linus Walleij <linus.walleij@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [linux-next:master 932/8744] arch/mips/ar7/gpio.c:19:19: error: field has incomplete type 'struct gpio_chip'
Date: Tue, 4 Apr 2023 09:22:36 +0200 [thread overview]
Message-ID: <CACRpkdaHRT7Gx3WZRzT+-6zsUmigHr4+56YCiUH6+T6ArV=Lhg@mail.gmail.com> (raw)
In-Reply-To: <202304040830.kPrP1Qew-lkp@intel.com>
On Tue, Apr 4, 2023 at 2:58 AM kernel test robot <lkp@intel.com> wrote:
> Note: the linux-next/master HEAD 31bd35b66249699343d2416658f57e97314a433a builds fine.
> It may have been fixed somewhere.
Yeah it is fixed somewhere:
commit 424b21e01aafc98a9c086f00b3ad1874302b92fc
Author: Arnd Bergmann <arnd@arndb.de>
Date: Wed Mar 8 15:52:53 2023 +0100
mips: ar7: include linux/gpio/driver.h
(...)
Yours,
Linus Walleij
prev parent reply other threads:[~2023-04-04 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 0:58 kernel test robot
2023-04-04 7:22 ` Linus Walleij [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='CACRpkdaHRT7Gx3WZRzT+-6zsUmigHr4+56YCiUH6+T6ArV=Lhg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-mm@kvack.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