From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Sergey 'Jin' Bostandzhyan" <jin@mediatomb.cc>,
"Heiko Stübner" <heiko@sntech.de>
Cc: "Daniel Golle" <daniel@makrotopia.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus
Date: Wed, 14 Aug 2024 13:34:13 +0200 [thread overview]
Message-ID: <D3FLPC79YN2S.34PAJFECP21X9@cknow.org> (raw)
In-Reply-To: <D3FLMBPACMF8.249JV2GI2QGHA@cknow.org>
[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]
On Wed Aug 14, 2024 at 1:30 PM CEST, Diederik de Haas wrote:
> On Wed Aug 14, 2024 at 1:21 PM CEST, Sergey 'Jin' Bostandzhyan wrote:
> > In case you tell me to go ahead with a v3 set, should it be in this
> > thread or not? I understood RESEND's should be new, but updates should
> > stay in the thread, right?
>
> No, a new series should be its own thread too.
More correctly and hopefully more clearly:
No, a new patch version (series) should be its own thread too.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Sergey 'Jin' Bostandzhyan" <jin@mediatomb.cc>,
"Heiko Stübner" <heiko@sntech.de>
Cc: "Daniel Golle" <daniel@makrotopia.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus
Date: Wed, 14 Aug 2024 13:34:13 +0200 [thread overview]
Message-ID: <D3FLPC79YN2S.34PAJFECP21X9@cknow.org> (raw)
In-Reply-To: <D3FLMBPACMF8.249JV2GI2QGHA@cknow.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Wed Aug 14, 2024 at 1:30 PM CEST, Diederik de Haas wrote:
> On Wed Aug 14, 2024 at 1:21 PM CEST, Sergey 'Jin' Bostandzhyan wrote:
> > In case you tell me to go ahead with a v3 set, should it be in this
> > thread or not? I understood RESEND's should be new, but updates should
> > stay in the thread, right?
>
> No, a new series should be its own thread too.
More correctly and hopefully more clearly:
No, a new patch version (series) should be its own thread too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-08-14 11:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 20:41 [PATCH 0/2] Add DTS for NanoPi R2S Plus Sergey Bostandzhyan
2024-07-31 20:41 ` [PATCH 1/2] arm64: dts: rockchip: Add DTS for FriendlyARM " Sergey Bostandzhyan
2024-07-31 20:41 ` [PATCH 2/2] dt-bindings: arm: rockchip: Add " Sergey Bostandzhyan
2024-08-01 8:10 ` Krzysztof Kozlowski
2024-08-01 17:57 ` [PATCH V2 0/2 RESEND] Add DTS for " Sergey Bostandzhyan
2024-08-01 17:57 ` Sergey Bostandzhyan
2024-08-01 17:57 ` [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM " Sergey Bostandzhyan
2024-08-01 17:57 ` Sergey Bostandzhyan
2024-08-04 0:27 ` Daniel Golle
2024-08-04 0:27 ` Daniel Golle
2024-08-05 8:59 ` Sergey 'Jin' Bostandzhyan
2024-08-05 8:59 ` Sergey 'Jin' Bostandzhyan
2024-08-10 19:11 ` Heiko Stübner
2024-08-10 19:11 ` Heiko Stübner
2024-08-14 11:21 ` Sergey 'Jin' Bostandzhyan
2024-08-14 11:21 ` Sergey 'Jin' Bostandzhyan
2024-08-14 11:30 ` Diederik de Haas
2024-08-14 11:30 ` Diederik de Haas
2024-08-14 11:34 ` Diederik de Haas [this message]
2024-08-14 11:34 ` Diederik de Haas
2024-08-14 11:36 ` Heiko Stübner
2024-08-14 11:36 ` Heiko Stübner
2024-08-14 12:24 ` Sergey 'Jin' Bostandzhyan
2024-08-14 12:24 ` Sergey 'Jin' Bostandzhyan
2024-08-14 13:53 ` Heiko Stübner
2024-08-14 13:53 ` Heiko Stübner
2024-08-01 17:57 ` [PATCH V2 2/2 RESEND] dt-bindings: arm: rockchip: Add " Sergey Bostandzhyan
2024-08-01 17:57 ` Sergey Bostandzhyan
2024-08-06 17:24 ` Rob Herring (Arm)
2024-08-06 17:24 ` Rob Herring (Arm)
2024-08-01 21:22 ` [PATCH V2 0/2 RESEND] Add DTS for " Heiko Stübner
2024-08-01 21:22 ` Heiko Stübner
2024-08-02 9:46 ` Bjoern A. Zeeb
2024-08-02 9:46 ` Bjoern A. Zeeb
2024-08-02 10:04 ` Sergey 'Jin' Bostandzhyan
2024-08-02 10:04 ` Sergey 'Jin' Bostandzhyan
2024-08-05 15:00 ` Rob Herring (Arm)
2024-08-05 15:00 ` Rob Herring (Arm)
2024-08-01 18:05 ` [PATCH 2/2] dt-bindings: arm: rockchip: Add " Sergey 'Jin' Bostandzhyan
2024-08-01 15:29 ` [PATCH 0/2] Add DTS for " Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 4:53 [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM " kernel test robot
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=D3FLPC79YN2S.34PAJFECP21X9@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jin@mediatomb.cc \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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 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.