All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Qu Wenruo <wqu@suse.com>
Subject: Re: linux-next: build failure after merge of the btrfs tree
Date: Wed, 22 Apr 2020 23:29:33 +0200	[thread overview]
Message-ID: <20200422212933.GS18421@suse.cz> (raw)
In-Reply-To: <20200421102520.53623f09@canb.auug.org.au>

On Tue, Apr 21, 2020 at 10:25:20AM +1000, Stephen Rothwell wrote:
> After merging the btrfs tree, today's linux-next build (x86_64
> allmodconfig) failed like this:

> Caused by commit
> 
>   8d80a063d508 ("btrfs: move on-disk structure definitions to btrfs_tree.h")
> 
> They should probably all be __u8 ...
> 
> I have applied the following patch for today.

I've removed the patch from the for-next branch.

  parent reply	other threads:[~2020-04-22 21:30 UTC|newest]

Thread overview: 32+ 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
2020-04-21  1:55       ` Stephen Rothwell
2020-04-22 21:29 ` David Sterba [this message]
2020-04-24  5:17   ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
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=20200422212933.GS18421@suse.cz \
    --to=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wqu@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.