From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Joakim Zhang <qiangqing.zhang@nxp.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "wg@grandegger.com" <wg@grandegger.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
Aisheng DONG <aisheng.dong@nxp.com>
Subject: Re: [PATCH V6 2/2] can: flexcan: add self wakeup support
Date: Mon, 26 Nov 2018 12:34:10 +0100 [thread overview]
Message-ID: <7b1215df-f1ea-c366-17ff-bc5265e58ffa@pengutronix.de> (raw)
In-Reply-To: <DB7PR04MB46180404F4201A8FAA52400FE6D70@DB7PR04MB4618.eurprd04.prod.outlook.com>
On 11/26/18 2:12 AM, Joakim Zhang wrote:
> Firstly, thanks for reviewing the patch. Then, I am confused to do
> upstream on "linux-can" or "linux-can-next" due to I find "linux-can"
> is more updated than "linux-can-next".
linux-can is for fixes aginat the current net/master.
linux-can-next is for new features against net-next/master.
I just updates both branches and pushed linux-can-next/testing, too,
which is going the be the next pull request.
regards,
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 |
next prev parent reply other threads:[~2018-11-26 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 8:35 [PATCH V6 0/2] can: flexcan: add can self wakeup support Joakim Zhang
2018-11-23 8:35 ` [PATCH V6 1/2] Documentation: can: flexcan: add stop mode property to device tree Joakim Zhang
2018-11-26 20:06 ` Rob Herring
2018-11-23 8:35 ` [PATCH V6 2/2] can: flexcan: add self wakeup support Joakim Zhang
2018-11-23 15:03 ` Marc Kleine-Budde
2018-11-26 1:12 ` Joakim Zhang
2018-11-26 11:34 ` Marc Kleine-Budde [this message]
2018-11-23 8:56 ` [PATCH V6 0/2] can: flexcan: add can " Aisheng DONG
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=7b1215df-f1ea-c366-17ff-bc5265e58ffa@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@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).