From: Oliver Bock <o.bock@fh-wolfenbuettel.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 1/1] usb: new driver for Cypress CY7C63xxx mirco controllers
Date: Tue, 13 Jun 2006 23:30:24 +0200 [thread overview]
Message-ID: <200606132330.24677.o.bock@fh-wolfenbuettel.de> (raw)
In-Reply-To: <20060613192304.GG27312@elf.ucw.cz>
Hi Pavel,
> > Hm, the chipset family is just called like that and there're at least
> > three other Cypress related drivers (cypress, cypress_m8 and cytherm)
> > with generic names. I think this name shows clearly what kind of device
> > it supports, doesn't it?
>
> cypress_63 might be unique and still easier to pronounce?
Hm, what about something related to the vendor "AK Modul-Bus Computer GmbH"?
I think my driver might (!) only work for their firmware implementations...
cypress_akmb
cypress_akmodbus
cypress_akmodulbus
The third would be my favourite. Are there any length restrictions for
driver/files names? Is it a problem to use parts of company names for this
purpose (I saw lego, rio, auerswald, etc.) or does one need to ask them for
permission in this case?
> > You mean the whole string (line) one character to the right, correct?
>
> Yes. It should be
>
> foo(BAR,
> BAZ).
>
> (You have it at few more places).
I changed it. I had the rule "only tabs for indentation" on my mind and tried
to choose the closest ;-) Now I first use tabs followed by spaces for
fine-tuning (if needed).
What about the macro discussion?
If there's any convention I'm happy to follow it...
Thanks,
Oliver
next prev parent reply other threads:[~2006-06-13 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 22:42 Oliver Bock
2006-06-09 22:49 ` Pavel Machek
2006-06-12 17:34 ` Oliver Bock
2006-06-13 19:23 ` Pavel Machek
2006-06-13 21:16 ` Greg KH
2006-06-18 15:52 ` Oliver Bock
2006-06-13 21:30 ` Oliver Bock [this message]
2006-06-13 22:18 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 20:57 Oliver Bock
2006-06-09 10:45 ` Pavel Machek
2006-06-09 22:50 ` Greg KH
2006-06-10 12:56 ` Oliver Bock
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=200606132330.24677.o.bock@fh-wolfenbuettel.de \
--to=o.bock@fh-wolfenbuettel.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
Powered by JetHome