From: Tom Rini <trini@konsulko.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 2/5] doc: develop: process: Make "Work flow of a Custodian" a subsection
Date: Wed, 21 Jan 2026 08:51:35 -0600 [thread overview]
Message-ID: <20260121145135.GS3416603@bill-the-cat> (raw)
In-Reply-To: <CAOf5uwkkkehBhMdHEKwbr00DCDJ2B+qe18kBRUJ=chox0NKLLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Wed, Jan 21, 2026 at 10:44:42AM +0100, Michael Nazzareno Trimarchi wrote:
> Hi Tom
>
> On Tue, Jan 20, 2026 at 11:35 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > Make the "Work flow of a Custodian" section be a subsection of the
> > Custodioans section.
> >
>
> You have just a typo here
Heinrich, can you fix this when applying please?
>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > doc/develop/process.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/doc/develop/process.rst b/doc/develop/process.rst
> > index 3bda5e6b51dd..f436a98433a7 100644
> > --- a/doc/develop/process.rst
> > +++ b/doc/develop/process.rst
> > @@ -233,7 +233,7 @@ feedback to the submitter of a patch about what is going on:
> > apply cleanly.
> >
> > Work flow of a Custodian
> > -------------------------
> > +^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > The normal flow of work in the U-Boot development process will look
> > like this:
> > --
> > 2.43.0
> >
>
> I'm fine with it
> Reviewed-by: Michael Trimarchi <michael@amarulasolutions.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-01-21 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 22:31 [PATCH 0/5] doc: develop: Document b4 for custodians Tom Rini
2026-01-20 22:31 ` [PATCH 1/5] doc: develop: process: Move Custodians section Tom Rini
2026-01-21 10:55 ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 2/5] doc: develop: process: Make "Work flow of a Custodian" a subsection Tom Rini
2026-01-21 9:44 ` Michael Nazzareno Trimarchi
2026-01-21 14:51 ` Tom Rini [this message]
2026-01-21 10:57 ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 3/5] doc: develop: codingstyle: Update b4 external link Tom Rini
2026-01-21 10:58 ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 4/5] doc: develop: sending_patches: Update link to patchwork Tom Rini
2026-01-21 10:59 ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 5/5] doc: develop: process: Document using b4 and patchwork for custodians Tom Rini
2026-01-21 11:16 ` Quentin Schulz
2026-01-21 15:06 ` Tom Rini
2026-01-26 13:17 ` Mattijs Korpershoek
2026-01-26 13:18 ` Mattijs Korpershoek
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=20260121145135.GS3416603@bill-the-cat \
--to=trini@konsulko.com \
--cc=michael@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.