From: Bich HEMON <bich.hemon@st.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"Jiri Slaby" <jslaby@suse.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Update interrupt names
Date: Tue, 6 Mar 2018 09:58:38 +0000 [thread overview]
Message-ID: <d855b529-be9b-13d9-8834-c2d0b7a16884@st.com> (raw)
In-Reply-To: <1519815044-22669-1-git-send-email-bich.hemon@st.com>
Hi all,
On 02/28/2018 11:51 AM, Bich HEMON wrote:
> This patchset updates existing stm32 usart driver by updating interrupt
> initialization by name.
>
> Bich Hemon (2):
> dt-bindings: serial: stm32: add wakeup option using note
> serial: stm32: update interrupt initialization
>
> Documentation/devicetree/bindings/serial/st,stm32-usart.txt | 4 ++++
> drivers/tty/serial/stm32-usart.c | 4 ++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
Please note that this patch set is abandoned. As Rob pointed that out,
the interrupt indices are fixed, so there is no need to keep these patches.
Best regards,
Bich
prev parent reply other threads:[~2018-03-06 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 10:51 Bich HEMON
2018-02-28 10:51 ` [PATCH 1/2] dt-bindings: serial: stm32: add wakeup option using note Bich HEMON
2018-03-06 0:52 ` Rob Herring
2018-02-28 10:51 ` [PATCH 2/2] serial: stm32: update interrupt initialization Bich HEMON
2018-02-28 15:40 ` Andy Shevchenko
2018-02-28 15:41 ` Andy Shevchenko
2018-03-06 0:50 ` Rob Herring
2018-03-06 9:58 ` Bich HEMON [this message]
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=d855b529-be9b-13d9-8834-c2d0b7a16884@st.com \
--to=bich.hemon@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®