From: Rob Landley <rob@landley.net>
To: Stefan Berger <stefanb@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH 5/5] fix rootfstype=tmpfs
Date: Thu, 9 Nov 2023 10:42:44 -0600 [thread overview]
Message-ID: <8f027b47-e778-15fc-0306-a5ae094f1070@landley.net> (raw)
In-Reply-To: <b74ea810-5b6c-404d-8cee-7d3d3922205e@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On 11/8/23 16:05, Stefan Berger wrote:
> On 11/1/23 09:10, Stefan Berger wrote:
>> On 2/21/23 16:04, Rob Landley wrote:
>>> Wire up rootfstype=tmpfs to force rootfs to be tmpfs even when you
>>> specify root=
>>>
>>> Initramfs automatically uses tmpfs (if available) when you DON'T
>>> specify a
>>> root= fallback root to mount over initramfs, but some people can't NOT do
>
> can't NOT -> cannot
The double negative was intentional for emphasis, hence the capitalization. They
are unable to refrain from doing. "Could you just... not do that?" "No, I cannot
not do that."
But if you want to phrase it differently, go ahead.
>>> that for some reason (old bootloaders), so let rootfstype=tmpfs
>>> override it.
>>>
>>> My original code tried to do this 10 years ago but got the test wrong,
>>> and nobody's corrected it since, so here you go...
>
> I think this sentence can be dropped.
If you like.
>>>
>>> Signed-off-by: Rob Landley <rob@landley.net>
>>
>> I would like to be able to have this for some work with OpenBMC and
>> ideally it would propagate to one of the recent kernels with a Fixes tag
>> like this?
>
> Can you repost this patch or should I do it?
They're more likely to listen to you.
Rob
[-- Attachment #2: patches.tgz --]
[-- Type: application/x-compressed-tar, Size: 8137 bytes --]
next prev parent reply other threads:[~2023-11-09 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:53 [PATCH 0/5] Patches used to build mkroot Rob Landley
2023-02-21 20:55 ` [PATCH 1/5] try generic compiler name "cc" before falling back to "gcc" Rob Landley
2023-02-23 5:31 ` Masahiro Yamada
2023-02-23 13:50 ` Rob Landley
2023-02-24 0:27 ` Masahiro Yamada
2023-02-21 20:56 ` [PATCH 2/5] X86-64 should not uniquely require a third ELF package to build Rob Landley
2023-02-21 23:12 ` Thomas Gleixner
2023-02-22 18:14 ` Rob Landley
2023-02-22 18:41 ` Thomas Gleixner
2023-02-21 20:57 ` [PATCH 3/5] Wire up CONFIG_DEVTMPFS_MOUNT to initramfs Rob Landley
2023-02-21 21:00 ` [PATCH 4/5] Replace timeconst.bc with mktimeconst.c Rob Landley
2023-02-21 23:53 ` Thomas Gleixner
2023-02-22 22:52 ` Rob Landley
2023-02-21 21:04 ` [PATCH 5/5] fix rootfstype=tmpfs Rob Landley
2023-11-01 13:10 ` Stefan Berger
2023-11-08 22:05 ` Stefan Berger
2023-11-09 16:42 ` Rob Landley [this message]
2023-11-09 16:46 ` Rob Landley
2023-11-09 16:55 ` Rob Landley
2023-02-23 20:35 ` [PATCH 0/5] Patches used to build mkroot Andrew Morton
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=8f027b47-e778-15fc-0306-a5ae094f1070@landley.net \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®