From: Qu Wenruo <wqu@suse•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: David Sterba <dsterba@suse•cz>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the btrfs tree
Date: Tue, 21 Apr 2020 09:33:56 +0800 [thread overview]
Message-ID: <10d92c2f-7120-18bb-1412-e3627d2d8f4c@suse.com> (raw)
In-Reply-To: <20200421111324.2148fe05@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
On 2020/4/21 上午9:13, Stephen Rothwell wrote:
> Hi Qu,
>
> On Tue, 21 Apr 2020 08:40:45 +0800 Qu Wenruo <wqu@suse•com> wrote:
>>
>> On 2020/4/21 上午8:25, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the btrfs tree, today's linux-next build (x86_64
>>> allmodconfig) failed like this:
>>>
>>> In file included from <command-line>:32:
>>
>> Any extra info?
>
> That is a build test of the uapi headers to make syre that they are
> self contained.
Any command to reproduce it?
As I want to avoid such problem in future development.
>
>> It builds fine in my environment, with older HEAD though.
>>
>> Is there any new commits which changed <linux/types.h> header?
>> As it should includes u8 typedef.
>
> My understanding is that you should only use the __ versions of the
> kernel types in uapi headers to avoid namespace contamination.
>
Thanks for the hint,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-21 1:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 0:25 linux-next: build failure after merge of the btrfs tree Stephen Rothwell
2020-04-21 0:40 ` Qu Wenruo
2020-04-21 1:13 ` Stephen Rothwell
2020-04-21 1:33 ` Qu Wenruo [this message]
2020-04-21 1:55 ` Stephen Rothwell
2020-04-22 21:29 ` David Sterba
2020-04-24 5:17 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2025-12-17 22:26 Stephen Rothwell
2025-12-18 12:14 ` David Sterba
2025-02-26 23:32 Stephen Rothwell
2025-02-27 9:40 ` David Sterba
2024-10-23 21:57 Stephen Rothwell
2024-10-23 22:28 ` Qu Wenruo
2024-10-24 0:47 ` David Sterba
2024-10-24 0:52 ` Qu Wenruo
2024-10-24 1:05 ` David Sterba
2024-10-24 1:00 ` Stephen Rothwell
2024-10-27 22:03 ` Stephen Rothwell
2024-10-29 16:21 ` David Sterba
2023-01-12 23:36 Stephen Rothwell
2023-01-13 10:59 ` David Sterba
2022-11-07 22:42 Stephen Rothwell
2022-11-08 11:21 ` David Sterba
2022-09-06 19:44 Stephen Rothwell
2022-08-21 23:44 Stephen Rothwell
2021-10-27 10:09 Stephen Rothwell
2021-10-29 8:28 ` Stephen Rothwell
2021-10-29 9:52 ` David Sterba
2021-10-29 10:50 ` David Sterba
[not found] ` <CAHp75VdXJEuY86pFC+bLoGbAYuGsA+KqEV-g4Dca25HHD-njHA@mail.gmail.com>
2021-10-29 12:14 ` David Sterba
2021-10-31 4:30 ` Stephen Rothwell
2021-10-08 4:03 Stephen Rothwell
2021-10-08 5:56 ` Qu Wenruo
2020-02-19 22:23 Stephen Rothwell
2020-02-21 11:30 ` David Sterba
2020-02-21 11:33 ` David Sterba
2015-08-21 0:42 Stephen Rothwell
2012-12-16 23:00 Stephen Rothwell
2012-12-17 0:15 ` Chris Mason
2012-12-17 2:52 ` Chris Mason
2012-12-17 3:13 ` Stephen Rothwell
2012-12-17 3:38 ` Chris Mason
2012-12-17 2:01 ` Chris Mason
2012-10-01 4:22 Stephen Rothwell
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=10d92c2f-7120-18bb-1412-e3627d2d8f4c@suse.com \
--to=wqu@suse$(echo .)com \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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