All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Romain Perier <romain.perier@gmail.com>
Cc: Stephen Boyd <sboyd@kernel.org>, Daniel Palmer <daniel@0x0f.com>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v5 1/1] clk: mstar: msc313 cpupll clk driver
Date: Wed, 5 Oct 2022 09:34:54 +0200	[thread overview]
Message-ID: <20221005073454.GA3728@1wt.eu> (raw)
In-Reply-To: <CABgxDoK-r_ENKo4qcB3PbCS2KOifHhzMvy1gWM=8yEsrH4JVvQ@mail.gmail.com>

On Wed, Oct 05, 2022 at 09:33:40AM +0200, Romain Perier wrote:
> Hi,
> 
> Quiet frankly I don't want to debate about this , as is it seems to be
> basically "the rule" (see
> https://www.kernel.org/doc/html/v6.0/process/submitting-patches.html).
> It is okay for you Willy, if I transform your tag to
> "Co-developed-by:" plus a "Signed-off-by" ? So Stephen can apply it ,
> and everyone is happy :)

Yes absolutely! I just wanted to avoid yet another round trip.
Many thanks Romain!

Willy

WARNING: multiple messages have this Message-ID (diff)
From: Willy Tarreau <w@1wt.eu>
To: Romain Perier <romain.perier@gmail.com>
Cc: Stephen Boyd <sboyd@kernel.org>, Daniel Palmer <daniel@0x0f.com>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v5 1/1] clk: mstar: msc313 cpupll clk driver
Date: Wed, 5 Oct 2022 09:34:54 +0200	[thread overview]
Message-ID: <20221005073454.GA3728@1wt.eu> (raw)
In-Reply-To: <CABgxDoK-r_ENKo4qcB3PbCS2KOifHhzMvy1gWM=8yEsrH4JVvQ@mail.gmail.com>

On Wed, Oct 05, 2022 at 09:33:40AM +0200, Romain Perier wrote:
> Hi,
> 
> Quiet frankly I don't want to debate about this , as is it seems to be
> basically "the rule" (see
> https://www.kernel.org/doc/html/v6.0/process/submitting-patches.html).
> It is okay for you Willy, if I transform your tag to
> "Co-developed-by:" plus a "Signed-off-by" ? So Stephen can apply it ,
> and everyone is happy :)

Yes absolutely! I just wanted to avoid yet another round trip.
Many thanks Romain!

Willy

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

  reply	other threads:[~2022-10-05  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 19:05 [PATCH RESEND v5 0/1] ARM: mstar: cpupll Romain Perier
2022-06-03 19:05 ` Romain Perier
2022-06-03 19:05 ` [PATCH RESEND v5 1/1] clk: mstar: msc313 cpupll clk driver Romain Perier
2022-06-03 19:05   ` Romain Perier
2022-09-30 19:17   ` Stephen Boyd
2022-09-30 19:17     ` Stephen Boyd
2022-09-30 19:35     ` Willy Tarreau
2022-09-30 19:35       ` Willy Tarreau
2022-10-05  7:33       ` Romain Perier
2022-10-05  7:33         ` Romain Perier
2022-10-05  7:34         ` Willy Tarreau [this message]
2022-10-05  7:34           ` Willy Tarreau
2022-10-05  7:35     ` Romain Perier
2022-10-05  7:35       ` Romain Perier

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=20221005073454.GA3728@1wt.eu \
    --to=w@1wt.eu \
    --cc=daniel@0x0f.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=romain.perier@gmail.com \
    --cc=sboyd@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.