[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141105113607.GD4007@shlinux1.ap.freescale.net>
Date: Wed, 5 Nov 2014 19:36:08 +0800
From: Dong Aisheng <b29396@...escale.com>
To: Varka Bhadram <varkabhadram@...il.com>
CC: <linux-can@...r.kernel.org>, <mkl@...gutronix.de>,
<wg@...ndegger.com>, <netdev@...r.kernel.org>,
<socketcan@...tkopp.net>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V2 1/4] can: m_can: update to support CAN FD features
On Wed, Nov 05, 2014 at 05:05:11PM +0530, Varka Bhadram wrote:
> Hi Dong Aisheng,
>
> On 11/05/2014 01:28 PM, Dong Aisheng wrote:
>
> >Bosch M_CAN is CAN FD capable device. This patch implements the CAN
> >FD features include up to 64 bytes payload and bitrate switch function.
> >1) Change the Rx FIFO and Tx Buffer to 64 bytes for support CAN FD
> > up to 64 bytes payload. It's backward compatible with old 8 bytes
> > normal CAN frame.
> >2) Allocate can frame or canfd frame based on EDL bit
> >3) Bitrate Switch function is disabled by default and will be enabled
> > according to CANFD_BRS bit in cf->flags.
> >
> >Signed-off-by: Dong Aisheng <b29396@...escale.com>
>
> In these four patches two of them are V1 and other two are V2.
>
> Is there any reason..?
>
Sorry for confusion.
Because some patches are already picked by Macr on the first round.
See below:
http://www.spinics.net/lists/netdev/msg302133.html
> How will you be able to generate like this by git format-patch..?
>
Generated as v2 and i manually changed the later two to v1 since they
are new.
Not sure if it's suitable to do like that. :-)
Regards
Dong Aisheng
> --
> Thanks and Regards,
> Varka Bhadram.
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists