From: Rob Landley <rob@landley.net>
To: Askar Safin <safinaskar@gmail.com>
Cc: Stefan Berger <stefanb@linux.ibm.com>,
gregkh@linuxfoundation.org, initramfs@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
zohar@linux.ibm.com
Subject: Re: [PATCH v3] rootfs: Fix support for rootfstype= when root= is given
Date: Mon, 1 Jan 2024 11:48:25 -0600 [thread overview]
Message-ID: <93564d28-5c56-6c8e-3052-0171c2bef43b@landley.net> (raw)
In-Reply-To: <CAPnZJGBdwSBeKUK-An8n-eDJdrrA-rnKPMX16cFDfwx8wxQiwA@mail.gmail.com>
On 12/30/23 18:46, Askar Safin wrote:
> On Sat, Dec 30, 2023 at 8:01 PM Rob Landley <rob@landley.net> wrote:
>> You want to add a new capability requiring a new build dependency in the
>
> Rob, who are you telling this to? To Stefan? It seems he doesn't
> propose any further changes. *I* did propose changes (i. e. adding
> rdrootfstype=), and I already wrote that I will not pursue further
I was trying to make sure we can support the motivating use case, and that there
aren't any actual blockers with the current API.
I don't ask things like "Do I have that right?" sarcastically: I am periodically
wrong about stuff. You all know your use case(s) better than I do, and I may not
have understood your attempt to communicate it to me.
I get a bit exasperated at "this thing that's been there for 10 years could
instead have been like this" because I think changing established kernel api is
_conceptually_ expensive (either we broke the old one or now we have to support
two), but "I still can't figure out how to make X work" means somebody still
needs help (up to and including actually motivating an API change, but more
commonly some userspace design work and/or a documentation update).
Thank you for clarifying. It looks like we're good here for the moment.
Rob
next prev parent reply other threads:[~2024-01-01 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 2:19 [PATCH v3] rootfs: Fix support for rootfstype= when root= is given Askar Safin
2023-12-21 9:30 ` Rob Landley
2023-12-21 22:58 ` Askar Safin
2023-12-29 16:39 ` Stefan Berger
2023-12-29 18:35 ` Rob Landley
2023-12-29 19:14 ` Stefan Berger
2023-12-30 17:08 ` Rob Landley
2023-12-31 0:46 ` Askar Safin
2024-01-01 17:48 ` Rob Landley [this message]
2024-01-03 6:18 ` Askar Safin
2023-12-31 16:03 ` Stefan Berger
2024-01-01 1:15 ` Askar Safin
2024-01-01 18:50 ` Rob Landley
2024-01-02 13:03 ` Stefan Berger
2024-01-04 6:06 ` Askar Safin
2024-01-04 16:38 ` Rob Landley
2023-12-30 2:10 ` Askar Safin
-- strict thread matches above, loose matches on Subject: below --
2023-11-20 1:12 Stefan Berger
2023-11-28 9:54 ` Greg KH
2023-11-28 12:18 ` Mimi Zohar
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=93564d28-5c56-6c8e-3052-0171c2bef43b@landley.net \
--to=rob@landley.net \
--cc=gregkh@linuxfoundation.org \
--cc=initramfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safinaskar@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).