All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Vincent Pelletier" <plr.vincent@gmail.com>,
	"Heiko Stübner" <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Qiu Wenbo <qiuwenbo@kylinos.com.cn>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	David Abdurachmanov <david.abdurachmanov@sifive.com>
Subject: Re: [PATCH] riscv: dts: sifive unmatched: Name gpio lines.
Date: Tue, 16 Nov 2021 12:05:32 +0100	[thread overview]
Message-ID: <ce1618f9-3b56-8670-387c-bca6181089b1@canonical.com> (raw)
In-Reply-To: <20211116101713.77a0df69@gmail.com>

On 16/11/2021 11:17, Vincent Pelletier wrote:
> Hello,
> 
> On Tue, 16 Nov 2021 10:39:04 +0100, Heiko Stübner <heiko@sntech.de> wrote:
>> Hi Vincent,
>>
>> Am Dienstag, 16. November 2021, 01:52:56 CET schrieb Vincent Pelletier:
>>> Follow the pin descriptions given in the version 3 of the board schematics.
>>>
>>> Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com>  
>>
>> when sending a patch series with "git format-patch -6" and friends will
>> automcatically generate x/y additions like "[PATCH 1/6]" and so on.
>>
>> Please try to keep them around when sending, as automated tools for patch
>> handling like "b4", stumble when they encounter a patch series without them.
> 
> Actually my intent was to not make this a series, as in my understanding
> independent patches should/may be submitted separately from each other.
> They just happen to be stacked, and in this order, in my working copy,
> but should not functionally have any dependency on one another (I
> believe they should even apply cleanly in any order).
> 

This should be a series because the patches, even though independent,
are logically connected/grouped as one work.

Best regards,
Krzysztof

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: "Vincent Pelletier" <plr.vincent@gmail.com>,
	"Heiko Stübner" <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Qiu Wenbo <qiuwenbo@kylinos.com.cn>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	David Abdurachmanov <david.abdurachmanov@sifive.com>
Subject: Re: [PATCH] riscv: dts: sifive unmatched: Name gpio lines.
Date: Tue, 16 Nov 2021 12:05:32 +0100	[thread overview]
Message-ID: <ce1618f9-3b56-8670-387c-bca6181089b1@canonical.com> (raw)
In-Reply-To: <20211116101713.77a0df69@gmail.com>

On 16/11/2021 11:17, Vincent Pelletier wrote:
> Hello,
> 
> On Tue, 16 Nov 2021 10:39:04 +0100, Heiko Stübner <heiko@sntech.de> wrote:
>> Hi Vincent,
>>
>> Am Dienstag, 16. November 2021, 01:52:56 CET schrieb Vincent Pelletier:
>>> Follow the pin descriptions given in the version 3 of the board schematics.
>>>
>>> Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com>  
>>
>> when sending a patch series with "git format-patch -6" and friends will
>> automcatically generate x/y additions like "[PATCH 1/6]" and so on.
>>
>> Please try to keep them around when sending, as automated tools for patch
>> handling like "b4", stumble when they encounter a patch series without them.
> 
> Actually my intent was to not make this a series, as in my understanding
> independent patches should/may be submitted separately from each other.
> They just happen to be stacked, and in this order, in my working copy,
> but should not functionally have any dependency on one another (I
> believe they should even apply cleanly in any order).
> 

This should be a series because the patches, even though independent,
are logically connected/grouped as one work.

Best regards,
Krzysztof

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2021-11-16 11:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  0:52 [PATCH] riscv: dts: sifive unmatched: Name gpio lines Vincent Pelletier
2021-11-16  0:52 ` Vincent Pelletier
2021-11-16  0:52 ` [PATCH] riscv: dts: sifive unmatched: Expose the board ID eeprom Vincent Pelletier
2021-11-16  0:52   ` Vincent Pelletier
2021-11-16  0:52 ` [PATCH] riscv: dts: sifive unmatched: Expose the PMIC sub-functions Vincent Pelletier
2021-11-16  0:52   ` Vincent Pelletier
2021-11-16  0:52 ` [PATCH] riscv: dts: sifive unmatched: Expose the FU740 core supply regulator Vincent Pelletier
2021-11-16  0:52   ` Vincent Pelletier
2021-11-16  9:53   ` Heiko Stübner
2021-11-16  9:53     ` Heiko Stübner
2021-11-16 11:08     ` Krzysztof Kozlowski
2021-11-16 11:08       ` Krzysztof Kozlowski
2021-11-16 11:13       ` Heiko Stübner
2021-11-16 11:13         ` Heiko Stübner
2021-11-16 10:44   ` Krzysztof Kozlowski
2021-11-16 10:44     ` Krzysztof Kozlowski
2021-11-16  0:53 ` [PATCH] riscv: dts: sifive unmatched: Fix regulator for board rev3 Vincent Pelletier
2021-11-16  0:53   ` Vincent Pelletier
2021-11-16  0:53 ` [PATCH] riscv: dts: sifive unmatched: Link the tmp451 with its power supply Vincent Pelletier
2021-11-16  0:53   ` Vincent Pelletier
2021-11-16 11:04   ` Krzysztof Kozlowski
2021-11-16 11:04     ` Krzysztof Kozlowski
2021-11-16  9:39 ` [PATCH] riscv: dts: sifive unmatched: Name gpio lines Heiko Stübner
2021-11-16  9:39   ` Heiko Stübner
2021-11-16 10:17   ` Vincent Pelletier
2021-11-16 10:17     ` Vincent Pelletier
2021-11-16 11:05     ` Krzysztof Kozlowski [this message]
2021-11-16 11:05       ` Krzysztof Kozlowski
2021-11-16 10:36 ` Krzysztof Kozlowski
2021-11-16 10:36   ` 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=ce1618f9-3b56-8670-387c-bca6181089b1@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=david.abdurachmanov@sifive.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=plr.vincent@gmail.com \
    --cc=qiuwenbo@kylinos.com.cn \
    --cc=robh+dt@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.