public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Frank Li <Frank.li@nxp.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] dt-bindings: pci: layerscape-pci: Convert to yaml file
Date: Thu, 8 Feb 2024 21:02:37 +0000	[thread overview]
Message-ID: <20240208-moisten-jaws-35a4935dca44@spud> (raw)
In-Reply-To: <ZcUyqaxf52GivQnd@lizhi-Precision-Tower-5810>

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

On Thu, Feb 08, 2024 at 02:59:37PM -0500, Frank Li wrote:
> On Thu, Feb 08, 2024 at 07:26:15PM +0000, Conor Dooley wrote:
> > On Wed, Feb 07, 2024 at 06:15:49PM -0500, Frank Li wrote:
> > > Convert layerscape pcie bind document to yaml file.
> > > 
> > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > 
> > Please don't send new versions before giving people a chance to finish
> > the discussion on the existing ones. This is not the first time in the
> > last few days I am asking you this. Nobody pays me to review DT
> > bindings, so you'll have to accept that I will take some time to reply.
> 
> Usb-glitch patch
> v1, I sent at Jan 19. 
> v2, I sent at Jan 21.
> v4, at Jan 24. 

Actually, I think I need to apologise. My first reply to you on v1 came
after you send the v4, so you didn't send new versions in that case
during a conversation - but sending 4 versions in 5 days is just going
to lead to people reviewing the old versions of a series. Please just
take a little more time between versions :)

> Generally, I send patch quick because I accepted their suggestion. It will
> be clear base on the new version. There are not big dissension need be
> discussed. 
> 
> About this one, I think first one have bigger problem because just convert
> txt to yaml file. Base on this version will be easy to discuss futher.

> The samething for me, nobody pays me to work this patch, which is my extra
> work.

Thanks for spending your free time working on binding conversions :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-02-08 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 23:15 [PATCH v2 1/1] dt-bindings: pci: layerscape-pci: Convert to yaml file Frank Li
2024-02-08 19:26 ` Conor Dooley
2024-02-08 19:59   ` Frank Li
2024-02-08 21:02     ` Conor Dooley [this message]
2024-05-17 11:05 ` Krzysztof Wilczyński

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=20240208-moisten-jaws-35a4935dca44@spud \
    --to=conor@kernel.org \
    --cc=Frank.li@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox