soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Rudraksha Gupta <guptarud@gmail.com>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	soc@kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: arm: qcom: Add Samsung Galaxy Express
Date: Mon, 29 May 2023 23:37:30 +0100	[thread overview]
Message-ID: <20230529-bonsai-during-37a47a528ff3@spud> (raw)
In-Reply-To: <CSZ46N3I9GM7.NON5KMJ66OK5@Latitude-E6420>

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

On Mon, May 29, 2023 at 06:28:05PM -0400, Rudraksha Gupta wrote:
> On Mon May 29, 2023 at 3:41 AM EDT, Konrad Dybcio wrote:

> > Please fix your email client:
> >
> > - wrap each line at about 80 characters
> > - don't trim messages unless they're very long or
> >   there's some other good reason
> > - Don't send v(n+1) as a reply to v(n), send it in a
> >   separate thread.
> >
> Gotcha, I will do that next time. Should I still send v2 in a separate
> thread?

That'd then be either [PATCH v3], or [RESEND PATCH v2]. Ideally v3 since
you will have added the tags you received on v2.
AFAIK Bjorn uses b4, which should be able to deal with the series as-is,
but sending a v3 with the Acks etc would not be a bad idea. You
should probably give it a couple days before doing that to see if it
gets picked up before doing that.

> Not sure if I should as I don't want to spam anyone.

Sending new revisions of patches as a new thread is not spamming, we
signed up to be maintainers, or get to email from the lists, after all.
Sending several revisions of the same patches in a day would be spamming
though, but that is not what we are talking about here ;)

Cheers,
Conor.

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

  reply	other threads:[~2023-05-29 22:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230527040905.stmnoshkdqgiaex6@ripper>
2023-05-28  0:10 ` [PATCH v2 0/4] Samsung Galaxy Express SGH-I437 Support Rudraksha Gupta
2023-05-30 13:21   ` Krzysztof Kozlowski
2023-05-28  0:10 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Add Samsung Galaxy Express Rudraksha Gupta
2023-05-28  8:51   ` Conor Dooley
2023-05-28 13:36     ` Rudraksha Gupta
2023-05-28 19:10       ` Conor Dooley
2023-05-29  7:41       ` Konrad Dybcio
2023-05-29 22:28         ` Rudraksha Gupta
2023-05-29 22:37           ` Conor Dooley [this message]
2023-05-29 22:50             ` Rudraksha Gupta
2023-05-30 12:57   ` Krzysztof Kozlowski
2023-05-28  0:10 ` [PATCH v2 2/4] dt-bindings: Add qcom,usb-hs-phy-msm8960 Rudraksha Gupta
2023-05-28  8:47   ` Conor Dooley
2023-05-30 13:22   ` Krzysztof Kozlowski
2023-05-31  2:49     ` Rudraksha Gupta
2023-05-31  2:56       ` Dmitry Baryshkov
2023-05-28  0:10 ` [PATCH v2 3/4] ARM: dts: qcom: msm8960: Add USB node Rudraksha Gupta
2023-05-30 13:22   ` Krzysztof Kozlowski
2023-05-28  0:10 ` [PATCH v2 4/4] ARM: dts: qcom: Add Samsung Galaxy Express support Rudraksha Gupta
2023-05-30 13:24   ` Krzysztof Kozlowski

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-bonsai-during-37a47a528ff3@spud \
    --to=conor@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guptarud@gmail.com \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=soc@kernel.org \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).