All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Gregory Clement <gregory.clement@bootlin.com>
Cc: "Pali Rohár" <pali@kernel.org>,
	linux-clk@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 3/6] serial: mvebu-uart: implement UART clock driver for configuring UART base clock
Date: Sun, 13 Feb 2022 22:36:27 +0100	[thread overview]
Message-ID: <20220213223627.72f6e797@thinkpad> (raw)
In-Reply-To: <20220211191238.2142-4-kabel@kernel.org>

On Fri, 11 Feb 2022 20:12:35 +0100
Marek Behún <kabel@kernel.org> wrote:

> For these reasons, this new UART clock driver does not use
> ioremap_resource(), but only ioremap() to prevent resource conflicts
> between UART clock driver and UART driver.
> ===

These three equal signs "===" shouldn't be there in the commit message,
it should be an empty line instead. I accidentaly forgot to remove it
while I was rewriting the commit message :-(.

Please let me know if I should resend this.

Marek

WARNING: multiple messages have this Message-ID (diff)
From: "Marek Behún" <kabel@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Gregory Clement <gregory.clement@bootlin.com>
Cc: "Pali Rohár" <pali@kernel.org>,
	linux-clk@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 3/6] serial: mvebu-uart: implement UART clock driver for configuring UART base clock
Date: Sun, 13 Feb 2022 22:36:27 +0100	[thread overview]
Message-ID: <20220213223627.72f6e797@thinkpad> (raw)
In-Reply-To: <20220211191238.2142-4-kabel@kernel.org>

On Fri, 11 Feb 2022 20:12:35 +0100
Marek Behún <kabel@kernel.org> wrote:

> For these reasons, this new UART clock driver does not use
> ioremap_resource(), but only ioremap() to prevent resource conflicts
> between UART clock driver and UART driver.
> ===

These three equal signs "===" shouldn't be there in the commit message,
it should be an empty line instead. I accidentaly forgot to remove it
while I was rewriting the commit message :-(.

Please let me know if I should resend this.

Marek

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

  reply	other threads:[~2022-02-13 21:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 19:12 [PATCH v8 0/6] serial: mvebu-uart: Support for higher baudrates Marek Behún
2022-02-11 19:12 ` Marek Behún
2022-02-11 19:12 ` [PATCH v8 1/6] math64: New DIV_U64_ROUND_CLOSEST helper Marek Behún
2022-02-11 19:12   ` Marek Behún
2022-02-11 19:12 ` [PATCH v8 2/6] dt-bindings: mvebu-uart: document DT bindings for marvell,armada-3700-uart-clock Marek Behún
2022-02-11 19:12   ` [PATCH v8 2/6] dt-bindings: mvebu-uart: document DT bindings for marvell, armada-3700-uart-clock Marek Behún
2022-02-11 19:12 ` [PATCH v8 3/6] serial: mvebu-uart: implement UART clock driver for configuring UART base clock Marek Behún
2022-02-11 19:12   ` Marek Behún
2022-02-13 21:36   ` Marek Behún [this message]
2022-02-13 21:36     ` Marek Behún
2022-02-11 19:12 ` [PATCH v8 4/6] dt-bindings: mvebu-uart: update information about UART clock Marek Behún
2022-02-11 19:12   ` Marek Behún
2022-02-11 19:12 ` [PATCH v8 5/6] arm64: dts: marvell: armada-37xx: add device node for UART clock and use it Marek Behún
2022-02-11 19:12   ` Marek Behún
2022-02-14 15:46   ` Gregory CLEMENT
2022-02-14 15:46     ` Gregory CLEMENT
2022-02-11 19:12 ` [PATCH v8 6/6] serial: mvebu-uart: implement support for baudrates higher than 230400 Bd Marek Behún
2022-02-11 19:12   ` Marek Behún
2022-02-19 15:26 ` [PATCH v8 0/6] serial: mvebu-uart: Support for higher baudrates Pali Rohár
2022-02-19 15:26   ` Pali Rohár

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=20220213223627.72f6e797@thinkpad \
    --to=kabel@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pali@kernel.org \
    --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.