From: Markus Elfring <Markus.Elfring@web.de>
To: Dong Zhihong <donmor3000@hotmail.com>,
loongarch@lists.linux.dev, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Binbin Zhou <zhoubinbin@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Wang Xuerui <kernel@xen0n.name>,
Youling Tang <tangyouling@loongson.cn>
Subject: Re: loongarch: Make CONFIG_CMDLINE work with CONFIG_CMDLINE_EXTEND and CONFIG_CMDLINE_BOOTLOADER
Date: Sun, 9 Jul 2023 20:13:02 +0200 [thread overview]
Message-ID: <fb5bd2d8-5a65-9687-8dff-cccd28e136c6@web.de> (raw)
In-Reply-To: <93faf53150732ac776e68e34709a9aa8c88b5944.camel@hotmail.com>
> Also, a feature shown in config should be functioning,
We may hope so.
> or be considered buggy
This can happen.
> and get fixed.
Such an action can occasionally become desirable.
Under which circumstances would you get into the mood to enhance descriptions
another bit (also according to the published Linux development requirements)
for the presented change possibilities?
Regards,
Markus
prev parent reply other threads:[~2023-07-09 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 13:32 [PATCH] loongarch: Make CONFIG_CMDLINE work with CONFIG_CMDLINE_EXTEND and CONFIG_CMDLINE_BOOTLOADER Dong Zhihong
2023-07-09 13:34 ` Randy Dunlap
2023-07-09 15:30 ` Huacai Chen
2023-07-09 17:35 ` donmor
2023-07-10 7:53 ` Huacai Chen
2023-07-10 15:10 ` donmor
2023-07-10 16:04 ` donmor
2023-07-09 15:43 ` Markus Elfring
2023-07-09 17:35 ` donmor
2023-07-09 18:13 ` Markus Elfring [this message]
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=fb5bd2d8-5a65-9687-8dff-cccd28e136c6@web.de \
--to=markus.elfring@web.de \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=donmor3000@hotmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=tangyouling@loongson.cn \
--cc=tglx@linutronix.de \
--cc=yangtiezhu@loongson.cn \
--cc=zhoubinbin@loongson.cn \
/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