Re: linux-next: build failure after merge of the vfs tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: linux-next: build failure after merge of the vfs tree
From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Tue, 10 Nov 2020 19:00:36 +0000
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux Next Mailing List <linux-next@xxxxxxxxxxxxxxx>
In-reply-to: <20201027045912.GG3576660@ZenIV.linux.org.uk>
References: <20201027151414.2018d5fd@canb.auug.org.au> <20201027045912.GG3576660@ZenIV.linux.org.uk>

On Tue, Oct 27, 2020 at 04:59:12AM +0000, Al Viro wrote:

> I'll rebase that branch on top of sparc tree tomorrow (and eventually I'd like
> it to go through the sparc tree anyway).

Done - sorry for disappearing ;-/

Follow-Ups:
- Re: linux-next: build failure after merge of the vfs tree
  - From: Stephen Rothwell

References:
- linux-next: build failure after merge of the vfs tree
  - From: Stephen Rothwell
- Re: linux-next: build failure after merge of the vfs tree
  - From: Al Viro

Prev by Date: Re: [PATCH][next] cpumask: allocate enough space for string and trailing '\0' char
Next by Date: Re: [PATCH][next] cpumask: allocate enough space for string and trailing '\0' char
Previous by thread: Re: linux-next: build failure after merge of the vfs tree
Next by thread: Re: linux-next: build failure after merge of the vfs tree
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Linux USB Development] [Yosemite News] [Linux SCSI]

Powered by Linux