From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Bakker <xc-racer2@live.ca>, alim.akhtar@samsung.com
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] ARM: dts: s5pv210: Bugfixes, features, and improvements
Date: Wed, 23 Mar 2022 11:52:00 +0100 [thread overview]
Message-ID: <2608d7bc-2c23-8c66-efcc-77d2e23dee61@kernel.org> (raw)
In-Reply-To: <CY4PR04MB05673676DA7E6E4BF275305ECB179@CY4PR04MB0567.namprd04.prod.outlook.com>
On 22/03/2022 21:21, Jonathan Bakker wrote:
> Sorry, it appears that I ran into connectivity issues part way through sending
> the patchset. Should I resend the entire series or is there a way to get
> git send-email to retry/continue?
With git send-email you can always send remaining patches with
--no-thread and --in-reply-to=XXX, providing valid message ID.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-23 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 20:11 [PATCH 0/7] ARM: dts: s5pv210: Bugfixes, features, and improvements Jonathan Bakker
2022-03-22 20:21 ` Jonathan Bakker
2022-03-23 10:52 ` Krzysztof Kozlowski [this message]
2022-03-27 18:08 ` [PATCH v2 0/5] " Jonathan Bakker
2022-04-09 16:52 ` Krzysztof Kozlowski
2022-03-27 18:08 ` [PATCH v2 1/5] ARM: dts: s5pv210: Remove spi-cs-high on panel in Aries Jonathan Bakker
2022-03-27 18:08 ` [PATCH v2 2/5] ARM: dts: s5pv210: Correct interrupt name for bluetooth " Jonathan Bakker
2022-03-27 18:08 ` [PATCH v2 3/5] ARM: dts: s5pv210: Adjust memory reg entries to match spec Jonathan Bakker
2022-03-27 18:08 ` [PATCH v2 4/5] ARM: dts: s5pv210: Adjust DMA node names " Jonathan Bakker
2022-03-27 18:08 ` [PATCH v2 5/5] ARM: dts: s5pv210: align DMA channels with dtschema Jonathan Bakker
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=2608d7bc-2c23-8c66-efcc-77d2e23dee61@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=xc-racer2@live.ca \
/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).