[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200731063316.GA5145@lst.de>
Date: Fri, 31 Jul 2020 08:33:16 +0200
From: Christoph Hellwig <hch@....de>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Christoph Hellwig <hch@....de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: add file system helpers that take kernel pointers for the init
code v4
On Fri, Jul 31, 2020 at 03:14:24AM +0100, Al Viro wrote:
> Christoph Hellwig (28):
> [snip]
> initramfs: switch initramfs unpacking to struct file based APIs
> initramfs: switch initramfs unpacking to struct file based APIs
> [snip]
>
> It's not a bisect hazard, of course, but if you don't fold those
> together, you might at least want to give the second one a different
> commit summary... I hadn't been able to find an analogue of #init_path on
> top of that either.
>
> As it is, #init-user-pointers is fine (aside of that SNAFU with unfolded
> pair of commits), and so's the contents of #init_path part following what
> used to be #init-user-pointers, but it'll be an awful mess on merge in
> the current shape.
>
> I can sort it out myself, if you don't mind that; again, I'm OK with
> the contents and I've no problem with doing reordering/folding.
I've fixed the folding issues in init-user-pointers and rebased init_path
on top of that. Feel free to pull it. I don't think it is worth
reposting.
Powered by blists - more mailing lists