From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Jonas Mark (ST-FIR/ENG1)" <Mark.Jonas@de.bosch.com>,
"ZHU Yi (ST-FIR/ENG1-Zhu)" <Yi.Zhu5@cn.bosch.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Andri Yngvason <andri.yngvason@marel.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: "hs@denx.de" <hs@denx.de>,
"RUAN Tingquan (ST-FIR/ENG1-Zhu)" <Tingquan.Ruan@cn.bosch.com>
Subject: Re: [PATCH 0/4] can: flexcan: fix state transition, suppress irq flooding
Date: Mon, 2 Oct 2017 12:12:45 +0200 [thread overview]
Message-ID: <ad3f6258-609c-bc1e-a26c-778dc792b463@pengutronix.de> (raw)
In-Reply-To: <da2a7a180eb8445f8fc6539aeca5d44e@SI-MBX1030.de.bosch.com>
[-- Attachment #1.1: Type: text/plain, Size: 745 bytes --]
On 10/02/2017 11:05 AM, Jonas Mark (ST-FIR/ENG1) wrote:
> Hello Wolfgang and Marc,
>
>> From 9253741b7d8bdd4fabe41a8dc2211869589f0f18 Mon Sep 17 00:00:00 2001
>> From: Zhu Yi <yi.zhu5@cn.bosch.com>
>> Date: Tue, 5 Sep 2017 16:09:04 +0800
>> Subject: [PATCH 0/4] can: flexcan: fix state transition, suppress irq flooding
>
> Is the patch set already on its way upstream or is there something we still need to do?
I'll push the series to upstream.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-10-02 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 9:05 [PATCH 0/4] can: flexcan: fix state transition, suppress irq flooding Jonas Mark (ST-FIR/ENG1)
2017-10-02 10:12 ` Marc Kleine-Budde [this message]
2017-10-02 16:02 ` AW: " Jonas Mark (ST-FIR/ENG1)
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 8:33 ZHU Yi (ST-FIR/ENG1-Zhu)
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=ad3f6258-609c-bc1e-a26c-778dc792b463@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Mark.Jonas@de.bosch.com \
--cc=Tingquan.Ruan@cn.bosch.com \
--cc=Yi.Zhu5@cn.bosch.com \
--cc=andri.yngvason@marel.com \
--cc=hs@denx.de \
--cc=linux-can@vger.kernel.org \
--cc=wg@grandegger.com \
/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).