mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Bootconfig: Updates for v7.0
Date: Mon, 16 Feb 2026 16:28:34 +0900	[thread overview]
Message-ID: <20260216162834.3556df04b3781893c69825bd@kernel.org> (raw)
In-Reply-To: <CAHk-=whY-N8kjm8kiFUV5Ei-8AuYw--EPGD-AR3Pd+5GTx2sAQ@mail.gmail.com>

On Fri, 13 Feb 2026 19:37:13 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Fri, 13 Feb 2026 at 15:35, Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> >   Note that this changes the bootconfig formatting but this should not
> >   fall under the don't break user space rule as users of bootconfig is
> >   for booting the kernel and not about applications running in the
> >   kernel's user space.
> 
> Note that the rule is about breaking *users*, not breaking user space per se.
> 
> It's obviously not about "user space applications", since about h alf
> of the kernel is about hardware interfaces. If you break a driver, you
> break the user expectations.
> 
> If some user setup breaks, things need fixing.
> 
> That said, I agree that this is not likely to break any user
> configuration, but I want to make it very clear that there are no
> excuses about "user space applications".

Thanks for the clarification, I'll be more careful for the rule.

>                Linus


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-02-16  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 23:35 Masami Hiramatsu
2026-02-14  3:37 ` Linus Torvalds
2026-02-16  7:28   ` Masami Hiramatsu [this message]
2026-02-14  3:44 ` pr-tracker-bot

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=20260216162834.3556df04b3781893c69825bd@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /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®