From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:work.headers.unaligned 2/2] util/arm-spe-decoder/arm-spe-pkt-decoder.c:14:10: fatal error: 'linux/unaligned.h' file not found
Date: Fri, 23 Aug 2024 07:30:01 +0100 [thread overview]
Message-ID: <20240823063001.GA1049718@ZenIV> (raw)
In-Reply-To: <ZsgKudBxLxfMvlCU@rli9-mobl>
On Fri, Aug 23, 2024 at 12:06:17PM +0800, kernel test robot wrote:
> Hi Al,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.headers.unaligned
> head: 5adcdf60b29da8386cab7bb157927fec96a46c42
> commit: 5adcdf60b29da8386cab7bb157927fec96a46c42 [2/2] move asm/unaligned.h to linux/unaligned.h
Try 6f0416d97dba.
prev parent reply other threads:[~2024-08-23 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 4:06 [viro-vfs:work.headers.unaligned 2/2] util/arm-spe-decoder/arm-spe-pkt-decoder.c:14:10: fatal error: 'linux/unaligned.h' file not found kernel test robot
2024-08-23 6:30 ` Al Viro [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=20240823063001.GA1049718@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).