From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
soc@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
olof@lixom.net, palmer@dabbelt.com, robh+dt@kernel.org,
arnd@arndb.de
Subject: Re: [PATCH v2] Documentation/process: add soc maintainer handbook
Date: Tue, 30 May 2023 23:26:22 +0100 [thread overview]
Message-ID: <20230530-paragraph-putdown-389d45fb16c5@spud> (raw)
In-Reply-To: <44a247a3-e349-94da-8235-1b6911463d78@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]
Hey Randy,
On Tue, May 30, 2023 at 08:28:44AM -0700, Randy Dunlap wrote:
> On 5/30/23 05:49, Conor Dooley wrote:
> > Recommended is also to install yamllint (used by dtschema when present).
>
> I don't see anything in Documentation/ about where to find yamllint...
> please.
Sounds like an unrelated fix to me ;)
> submaintainers and sub-directories ? hm.
I had sub-maintainers before being asked to change! I think that
subdirectories is correct though & the hyphenated form is incorrect.
> > +named $soc.dtsi, for example, jh7100.dtsi. Integration details, that will vary
> > +from board to board, are described in $soc-$board.dtsi. An example of this is
> > +jh7100-beaglev-starlight.dts. Often many boards are variations on a theme, and
>
> ^^^ Why not dtsi, like the sentence before says?
> or is the $soc-$board.dtsi wrong?
$soc-$board.dtsi is wrong.
> > +Another common way to split up changes is to send an early pull request with the
> > +majority of the changes at some point between rc1 and rc4, following up with one
> > +or more smaller pull requests towards the end of the cycle that can add late
> > +changes or address problems idenfied while testing the first set.
>
> identified
Surprised nvim didn't whinge about that one.
Thanks for pointing out the wee mistakes all over the place,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
soc@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
olof@lixom.net, palmer@dabbelt.com, robh+dt@kernel.org,
arnd@arndb.de
Subject: Re: [PATCH v2] Documentation/process: add soc maintainer handbook
Date: Tue, 30 May 2023 23:26:22 +0100 [thread overview]
Message-ID: <20230530-paragraph-putdown-389d45fb16c5@spud> (raw)
In-Reply-To: <44a247a3-e349-94da-8235-1b6911463d78@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Hey Randy,
On Tue, May 30, 2023 at 08:28:44AM -0700, Randy Dunlap wrote:
> On 5/30/23 05:49, Conor Dooley wrote:
> > Recommended is also to install yamllint (used by dtschema when present).
>
> I don't see anything in Documentation/ about where to find yamllint...
> please.
Sounds like an unrelated fix to me ;)
> submaintainers and sub-directories ? hm.
I had sub-maintainers before being asked to change! I think that
subdirectories is correct though & the hyphenated form is incorrect.
> > +named $soc.dtsi, for example, jh7100.dtsi. Integration details, that will vary
> > +from board to board, are described in $soc-$board.dtsi. An example of this is
> > +jh7100-beaglev-starlight.dts. Often many boards are variations on a theme, and
>
> ^^^ Why not dtsi, like the sentence before says?
> or is the $soc-$board.dtsi wrong?
$soc-$board.dtsi is wrong.
> > +Another common way to split up changes is to send an early pull request with the
> > +majority of the changes at some point between rc1 and rc4, following up with one
> > +or more smaller pull requests towards the end of the cycle that can add late
> > +changes or address problems idenfied while testing the first set.
>
> identified
Surprised nvim didn't whinge about that one.
Thanks for pointing out the wee mistakes all over the place,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
soc@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
olof@lixom.net, palmer@dabbelt.com, robh+dt@kernel.org,
arnd@arndb.de
Subject: Re: [PATCH v2] Documentation/process: add soc maintainer handbook
Date: Tue, 30 May 2023 23:26:22 +0100 [thread overview]
Message-ID: <20230530-paragraph-putdown-389d45fb16c5@spud> (raw)
In-Reply-To: <44a247a3-e349-94da-8235-1b6911463d78@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]
Hey Randy,
On Tue, May 30, 2023 at 08:28:44AM -0700, Randy Dunlap wrote:
> On 5/30/23 05:49, Conor Dooley wrote:
> > Recommended is also to install yamllint (used by dtschema when present).
>
> I don't see anything in Documentation/ about where to find yamllint...
> please.
Sounds like an unrelated fix to me ;)
> submaintainers and sub-directories ? hm.
I had sub-maintainers before being asked to change! I think that
subdirectories is correct though & the hyphenated form is incorrect.
> > +named $soc.dtsi, for example, jh7100.dtsi. Integration details, that will vary
> > +from board to board, are described in $soc-$board.dtsi. An example of this is
> > +jh7100-beaglev-starlight.dts. Often many boards are variations on a theme, and
>
> ^^^ Why not dtsi, like the sentence before says?
> or is the $soc-$board.dtsi wrong?
$soc-$board.dtsi is wrong.
> > +Another common way to split up changes is to send an early pull request with the
> > +majority of the changes at some point between rc1 and rc4, following up with one
> > +or more smaller pull requests towards the end of the cycle that can add late
> > +changes or address problems idenfied while testing the first set.
>
> identified
Surprised nvim didn't whinge about that one.
Thanks for pointing out the wee mistakes all over the place,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-30 22:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:49 [PATCH v2] Documentation/process: add soc maintainer handbook Conor Dooley
2023-05-30 12:49 ` Conor Dooley
2023-05-30 12:49 ` Conor Dooley
2023-05-30 13:02 ` Jonathan Corbet
2023-05-30 13:02 ` Jonathan Corbet
2023-05-30 13:02 ` Jonathan Corbet
2023-05-30 13:12 ` Conor Dooley
2023-05-30 13:12 ` Conor Dooley
2023-05-30 13:12 ` Conor Dooley
2023-05-30 13:14 ` Krzysztof Kozlowski
2023-05-30 13:14 ` Krzysztof Kozlowski
2023-05-30 13:14 ` Krzysztof Kozlowski
2023-05-30 15:28 ` Randy Dunlap
2023-05-30 15:28 ` Randy Dunlap
2023-05-30 15:28 ` Randy Dunlap
2023-05-30 22:26 ` Conor Dooley [this message]
2023-05-30 22:26 ` Conor Dooley
2023-05-30 22:26 ` Conor Dooley
2023-05-31 6:30 ` Bagas Sanjaya
2023-05-31 6:30 ` Bagas Sanjaya
2023-05-31 6:30 ` Bagas Sanjaya
2023-05-31 6:51 ` Krzysztof Kozlowski
2023-05-31 6:51 ` Krzysztof Kozlowski
2023-05-31 6:51 ` Krzysztof Kozlowski
2023-05-31 12:22 ` Bagas Sanjaya
2023-05-31 12:22 ` Bagas Sanjaya
2023-05-31 12:22 ` Bagas Sanjaya
2023-05-31 9:41 ` Conor Dooley
2023-05-31 9:41 ` Conor Dooley
2023-05-31 9:41 ` Conor Dooley
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=20230530-paragraph-putdown-389d45fb16c5@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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 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.