From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: About adding a new CAN-FD driver...
Date: Fri, 18 Nov 2016 10:13:54 +0100 [thread overview]
Message-ID: <839d85dc-6532-eb96-707e-c5c0ab552b2e@peak-system.com> (raw)
In-Reply-To: <35164f73-1c31-1c80-d521-f2ab7ef68a00@hartkopp.net>
Hello Oliver,
> linux/include/linux/can/ip-core/
++
Regards,
Stéphane
Le 17/11/2016 à 21:20, Oliver Hartkopp a écrit :
> Hi Stephane,
>
> On 11/17/2016 11:22 AM, Stephane Grosjean wrote:
>> I'm almost ready for pushing the stuff about CAN-FD over our PCIe boards
>> but I'm back to you before, because in one of your previous email, you
>> talked about "linux/include/linux/can/dev" directory as the better place
>> to put a common header file for all of our CAN-FD interfaces.
>>
>> AFAIK this directory does not exist so far... Did you actually mean
>> "linux/include/linux/can"? Or did you expect me to create the "dev"
>> subdir with pushing the corresponding patch?
>
> Yes. The latter.
>
> I think putting controller specific include files directly into
> "linux/include/linux/can" is wrong in the way that the platform
> specific content has a separate directory too.
>
> My initial suggestion was
>
> linux/include/linux/can/dev/
>
> but we may also think of
>
> linux/include/linux/can/controller/
> linux/include/linux/can/ctrl/
> linux/include/linux/can/ip-core/
> linux/include/linux/can/ctrl-core/
> linux/include/linux/can/can-core/
>
> 'ip-core' seems a good name too as it reflects the CAN controller
> specific characteristics (e.g. memory register layout).
>
> What would you suggest as directory name?
>
> Regards,
> Oliver
>
--
PEAK-System Technik GmbH
Sitz der Gesellschaft Darmstadt - HRB 9183
Geschaeftsfuehrung: A.Gach, U.Wilhelm
--
prev parent reply other threads:[~2016-11-18 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 9:42 About adding a new CAN-FD driver Stephane Grosjean
2016-10-18 7:15 ` Oliver Hartkopp
2016-10-25 7:01 ` Stephane Grosjean
2016-10-25 8:44 ` Oliver Hartkopp
2016-11-17 10:22 ` Stephane Grosjean
2016-11-17 20:20 ` Oliver Hartkopp
2016-11-18 9:13 ` Stephane Grosjean [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=839d85dc-6532-eb96-707e-c5c0ab552b2e@peak-system.com \
--to=s.grosjean@peak-system.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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