linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev,
	James McGregor <jamcgregor@protonmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: input: sun4i-lradc-keys: Add H616 compatible
Date: Tue, 23 Apr 2024 13:51:06 +0100	[thread overview]
Message-ID: <20240423135106.02ab4473@donnerap.manchester.arm.com> (raw)
In-Reply-To: <f2021c5d-25fa-4bdf-8f8c-b0bc271eb54e@linaro.org>

On Tue, 23 Apr 2024 14:18:23 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:

Hi,

> On 23/04/2024 12:15, Andre Przywara wrote:
> > On Mon, 22 Apr 2024 17:45:10 +0100
> > Andre Przywara <andre.przywara@arm.com> wrote:
> > 
> > Hi,
> >   
> >> From: James McGregor <jamcgregor@protonmail.com>
> >>
> >> The Allwinner H616 SoC has an LRADC which is compatible with the
> >> versions in existing SoCs.
> >> Add a compatible string for H616, with the R329 fallback. This is the
> >> same as the D1, so put them into an enum.
> >>
> >> Signed-off-by: James McGregor <jamcgregor@protonmail.com>
> >> Signed-off-by: Andre Przywara <andre.przywara@arm.com>  
> > 
> > Compared the descriptions in the manual between the R392 and the H616, they
> > look the same:
> > 
> > Reviewed-by: Andre Przywara <andre.przywara@arm.com>  
> 
> Why do you review your own patches? Does it mean that you contribute
> code which you did not review before?

I just merely sent the code on behalf of James, because he had trouble
with the email setup (Protonmail has no SMTP), but didn't want to delay
the post any longer.

> This is odd process.

I agree, I would have liked it more if James would have sent it himself,
and then my review would look more natural, but with my review I
wanted to explicitly point out the technical correctness. Besides: I found
this ordering issue in the other patch only after sending, so needed to
somehow respond anyway.
Also I wanted to make the process transparent: someone posts a patch (in
this case via a proxy), then it gets reviewed.

> Your Review is implied by sending the patch.

Is that really true? I was under the impression that sending is
independent from review. I mean I doubt that every maintainer sending
patches up the chain (when they add their SoB) implies a *review*? Surely
they do agree on the patch (also typically expressed by an Ack), otherwise
they wouldn't send it, but a "review" is still a different thing.
The Linux history has both Rb + SoB from the same person and just SoB
signatures, so I assume that it's not implied.

> And you have there SoB which indicates you sent it...

Yes, but SoB just means I sign off on the legal aspects: that I got the
patches legally, compliant with the GPL, and that I am fine with and
allowed to release them under GPL conditions.
That does not include any code review aspect, AFAICT.

Happy to hear other opinions, but this is my interpretation.

Cheers,
Andre

  reply	other threads:[~2024-04-23 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:45 [PATCH 0/2] arm64: dts: allwinner: H616: Add LRADC Andre Przywara
2024-04-22 16:45 ` [PATCH 1/2] dt-bindings: input: sun4i-lradc-keys: Add H616 compatible Andre Przywara
2024-04-23 10:15   ` Andre Przywara
2024-04-23 12:18     ` Krzysztof Kozlowski
2024-04-23 12:51       ` Andre Przywara [this message]
2024-04-23 14:59         ` Krzysztof Kozlowski
2024-04-23 15:14           ` Krzysztof Kozlowski
2024-04-24 10:55           ` Andre Przywara
2024-04-24 17:56             ` Krzysztof Kozlowski
2024-04-23 14:32   ` Rob Herring
2024-04-22 16:45 ` [PATCH 2/2] arm64: dts: allwinner: h616: Add LRADC node Andre Przywara
2024-04-23 10:11   ` Andre Przywara

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=20240423135106.02ab4473@donnerap.manchester.arm.com \
    --to=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=jamcgregor@protonmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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).