From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-usb@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [usb:usb-testing 12/23] arch/arm/mach-s3c/devs.c:30:10: fatal error: 'linux/platform_data/s3c-hsudc.h' file not found
Date: Sat, 22 Oct 2022 22:58:51 +0200 [thread overview]
Message-ID: <7e16694e-c52a-4e8f-b138-e22c8ed3f136@app.fastmail.com> (raw)
In-Reply-To: <202210230210.NvXmltv5-lkp@intel.com>
On Sat, Oct 22, 2022, at 20:04, kernel test robot wrote:
>
> All errors (new ones prefixed by >>):
>
>>> arch/arm/mach-s3c/devs.c:30:10: fatal error: 'linux/platform_data/s3c-hsudc.h' file not found
> #include <linux/platform_data/s3c-hsudc.h>
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ah right, so the patch that removed the #include is in a separate branch
and not yet in linux-next. It might be easier if I just take this patch
through the soc tree as well.
Arnd
next prev parent reply other threads:[~2022-10-22 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 18:04 [usb:usb-testing 12/23] arch/arm/mach-s3c/devs.c:30:10: fatal error: 'linux/platform_data/s3c-hsudc.h' file not found kernel test robot
2022-10-22 20:58 ` Arnd Bergmann [this message]
2022-10-23 12:35 ` Greg Kroah-Hartman
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=7e16694e-c52a-4e8f-b138-e22c8ed3f136@app.fastmail.com \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@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