From: Conor Dooley <conor@kernel.org>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Paul Burton" <paulburton@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: mips: Add bindings for TP-Link HC220 G5 v1 board
Date: Mon, 29 May 2023 23:08:05 +0100 [thread overview]
Message-ID: <20230529-justify-runaround-a1dc64980ece@spud> (raw)
In-Reply-To: <ZHUe9RJfweNBAU0K@bart.dudau.co.uk>
[-- Attachment #1: Type: text/plain, Size: 2300 bytes --]
On Mon, May 29, 2023 at 10:53:57PM +0100, Liviu Dudau wrote:
> On Mon, May 29, 2023 at 10:00:20PM +0100, Conor Dooley wrote:
> > Two process things:
> > - Please run get_maintainer.pl against the current git tree - you seem
> > to have missed 2 of the 3 dt-bindings maintainers. I don't mind my
> > omission, but omitting Krzysztof means you're submitting patches based
> > on a tree that is over a year old.
>
> Appologies for that, I should have check get_maintainer.pl rather than looking
> at the output of git log for the file.
Yeah, git log ain't the way to do things ;)
>
> > - Please don't send a v2 in reply to the v1.
>
> Sorry, I'm not sure why that makes any difference. Reason for sending it as a
> reply was the fact that last conversation was more than two weeks ago, people
> might have forgot the context. This way it's all in one thread.
That's fine, just include a link to v1 on lore for anyone that cares
about the context, like so:
https://lore.kernel.org/all/20230529150833.526084-1-liviu@dudau.co.uk/
I knew this mail had been sent today because I noticed at the time that
you'd only CCed Rob but I remembered nothing of the subject line since
I saw it hours ago. Look how far back in my mailbox it ended up because
of being sent as a reply to the v1, and that mailbox only contains
emails from the devicetree list!
4380 May 29 Liviu Dudau (7.6K) │ ┌─>[PATCH v2 1/2] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board
4381 T May 29 Liviu Dudau (5.8K) │ │ ┌─>
4382 sF May 29 To Liviu Dudau (6.8K) │ │ ┌─>
4383 May 29 Liviu Dudau (4.6K) │ ├─>[PATCH v2 2/2] dt-bindings: mips: Add bindings for TP-Link HC220 G5 v1 board
4384 May 29 Liviu Dudau (4.7K) │ ┌─>[PATCH v2 0/2] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board
4385 May 12 Arınç ÜNAL ( 12K) │ ┌─>
4386 May 11 Liviu Dudau ( 10K) │ ┌─>
4387 May 11 Arınç ÜNAL ( 10K) ├─>
4388 May 09 Liviu Dudau (7.8K) [PATCH] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board.
Some patch application & CI tools apparently also get confused, but I
dunno what those tools are.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-29 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 20:01 [PATCH] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board Liviu Dudau
2023-05-11 13:41 ` Arınç ÜNAL
2023-05-11 16:03 ` Liviu Dudau
2023-05-12 6:40 ` Arınç ÜNAL
2023-05-29 15:08 ` [PATCH v2 0/2] " Liviu Dudau
2023-05-29 15:08 ` [PATCH v2 1/2] " Liviu Dudau
2023-05-29 15:55 ` Liviu Dudau
2023-06-03 12:06 ` Arınç ÜNAL
2023-06-04 21:30 ` Liviu Dudau
2023-06-05 7:28 ` Arınç ÜNAL
2023-06-03 12:10 ` Arınç ÜNAL
2023-05-29 15:08 ` [PATCH v2 2/2] dt-bindings: mips: Add bindings " Liviu Dudau
2023-05-29 21:00 ` Conor Dooley
2023-05-29 21:53 ` Liviu Dudau
2023-05-29 22:08 ` Conor Dooley [this message]
2023-05-30 3:35 ` Sergio Paracuellos
2023-05-11 13:43 ` [PATCH] mips: dts: ralink: Add support " Arınç ÜNAL
2023-05-11 13:59 ` Arınç ÜNAL
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=20230529-justify-runaround-a1dc64980ece@spud \
--to=conor@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).