From: Wolfgang Grandegger <wg@grandegger.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Linux-CAN <linux-can@vger.kernel.org>,
"bhupesh.sharma" <bhupesh.sharma@st.com>,
Tomoya MORINAGA <tomoya.rohm@gmail.com>
Subject: Re: [RFC/PATCH] c_can: add driver for the PCH CAN controller
Date: Thu, 23 Feb 2012 10:27:09 +0100 [thread overview]
Message-ID: <4F46066D.60601@grandegger.com> (raw)
In-Reply-To: <1626144.8BPv1GvbeG@ws-stein>
Hi Alexander,
On 02/23/2012 09:27 AM, Alexander Stein wrote:
> Hello Wolfgang,
>
> Am Mittwoch, 22. Februar 2012, 13:57:36 schrieb Wolfgang Grandegger:
>> For maintenance reasons, this diver should replace the "pch_can" driver
>> sooner than later as it uses the same CAN controller core. I named it
>> "pch_pci". Maybe "pch_can" would be more appropriate (common). This
>> patch is for 2.6.39, but likely it applies fine also to more recent
>> versions of the Linux kernel.
>>
>> Alexander, Tomoya, or anybody else, it would be nice if you could test
>> this patch and give some feedback. Thanks.
>
> What is the current state of c_can? Are there known bugs/issues?
Bhupes said that he has a series of changes for the C_CAN driver but I
don't know if they fix serious bugs. Apart from that, there are no
pending issues, IIRC.
Wolfgang.
next prev parent reply other threads:[~2012-02-23 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 12:57 [RFC/PATCH] c_can: add driver for the PCH CAN controller Wolfgang Grandegger
2012-02-23 0:13 ` Tomoya MORINAGA
2012-02-23 7:44 ` Wolfgang Grandegger
2012-02-23 8:08 ` Tomoya MORINAGA
2012-02-23 9:28 ` Wolfgang Grandegger
2012-02-23 8:27 ` Alexander Stein
2012-02-23 9:27 ` Wolfgang Grandegger [this message]
2012-02-23 9:48 ` Bhupesh SHARMA
2012-02-23 9:56 ` Alexander Stein
2012-02-23 10:00 ` Bhupesh SHARMA
2012-03-07 7:31 ` Alexander Stein
2012-03-12 17:53 ` Wolfgang Grandegger
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=4F46066D.60601@grandegger.com \
--to=wg@grandegger.com \
--cc=alexander.stein@systec-electronic.com \
--cc=bhupesh.sharma@st.com \
--cc=linux-can@vger.kernel.org \
--cc=tomoya.rohm@gmail.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 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.