linux-kernel - Re: [PATCH v3] Documentation: bootconfig: Update boot configuration documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200302150802.348b814e@gandalf.local.home>
Date:   Mon, 2 Mar 2020 15:08:02 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Markus Elfring <Markus.Elfring@....de>
Subject: Re: [PATCH v3] Documentation: bootconfig: Update boot configuration
 documentation

On Mon, 2 Mar 2020 12:50:33 -0700
Jonathan Corbet <corbet@....net> wrote:

> On Mon,  2 Mar 2020 17:03:48 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
> 
> > Update boot configuration documentation.
> > 
> >  - Not using "config" abbreviation but configuration or description.
> >  - Rewrite descriptions of node and its maxinum number.
> >  - Add a section of use cases of boot configuration.
> >  - Move how to use bootconfig to earlier section.
> >  - Fix some typos, indents and format mistakes.
> > 
> > Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
> > ---
> > Changes in v3:
> >  - Specify that comments also count in size.
> >  - Fix a confusing sentence.
> >  - Add O=<builddir> to make command.
> > Changes in v2:
> >  - Fixes additional typos (Thanks Markus and Randy!)
> >  - Change a section title to "Tree Structured Key".
> > ---  
> 
> So I tried to apply this but failed - it's built on other changes to
> bootconfig.rst that went into linux-next via Steve's tree.  So Steve,
> would you like to take this one too?

All my changes in linux-next have already hit Linus's tree. I haven't
started pushing my next merge window changes yet. Are you up to date with
Linus?

-- Steve