From: Heiko Stuebner <heiko@sntech.de>
To: Greg KH <gregkh@linuxfoundation.org>,
Quentin Schulz <foss+kernel@0leil.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
quentin.schulz@theobroma-systems.com
Subject: Re: [PATCH] arm64: dts: rockchip: lower rk3399-puma-haikou SD controller clock frequency
Date: Wed, 19 Oct 2022 19:15:38 +0200 [thread overview]
Message-ID: <8130714.T7Z3S40VBb@phil> (raw)
In-Reply-To: <52349f5d-661f-3e38-9745-01a84ddf820f@theobroma-systems.com>
Hi Quentin,
Am Mittwoch, 19. Oktober 2022, 17:59:54 CEST schrieb quentin.schulz@theobroma-systems.com:
> Hi Greg,
>
> On 10/19/22 4:56 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Oct 19, 2022 at 04:27:27PM +0200, Quentin Schulz wrote:
> > > From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> > >
> > > From: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
> >
> > You can not have 2 authors :(
> >
>
> That's a bug in b4 and my patch submission/mail sending workflow, I'll sort something out with the b4 community and send a new version of the patch soon. Thanks for the heads up!
I guess, Jakob is the original author?
If so, I can simply drop your authorship.
Heiko
>
> [...]
>
> > It has to be accepted before you are done :)
> >
>
> A "small" detail :)
>
> Cheers,
> Quentin
>
next prev parent reply other threads:[~2022-10-19 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:27 [PATCH] arm64: dts: rockchip: lower rk3399-puma-haikou SD controller clock frequency Quentin Schulz
2022-10-19 14:56 ` Greg KH
2022-10-19 15:59 ` quentin.schulz
2022-10-19 17:15 ` Heiko Stuebner [this message]
2022-10-20 8:32 ` Quentin Schulz
2022-10-20 9:49 ` Heiko Stuebner
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=8130714.T7Z3S40VBb@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=foss+kernel@0leil.net \
--cc=gregkh@linuxfoundation.org \
--cc=jakob.unterwurzacher@theobroma-systems.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.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).