From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Greg KH <greg@kroah.com>
Cc: Alon Ziv <alon+git@nolaviz.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Add Opticon OPN2001 write support
Date: Sun, 10 Oct 2010 17:58:39 +0400 [thread overview]
Message-ID: <4CB1C68F.1080905@mvista.com> (raw)
In-Reply-To: <20101010123453.GA21060@kroah.com>
Hello.
On 10/10/10 16:34, Greg KH wrote:
>>> OPN2001 expects write operations to arrive as a vendor-specific command
>>> through the control pipe (instead of using a separate bulk-out pipe).
>>> Signed-off-by: Alon Ziv<alon-git@nolaviz.org>
>>> ---
>>> drivers/usb/serial/opticon.c | 30 ++++++++++++++++++++++++++----
>>> 1 files changed, 26 insertions(+), 4 deletions(-)
>>> diff --git a/drivers/usb/serial/opticon.c b/drivers/usb/serial/opticon.c
>>> index 9ff19c8..4fe7c3d 100644
>>> --- a/drivers/usb/serial/opticon.c
>>> +++ b/drivers/usb/serial/opticon.c
>> [...]
>>> + } else {
>>> + struct usb_ctrlrequest *dr;
>>> +
>>> + dr = kmalloc(sizeof(struct usb_ctrlrequest), GFP_NOIO);
>> sizeof(*dr) is a preferred form.
> No, people disagree on this, there is no 'preferred' form, you are free
> to use either way.
Please refer to the CodingStyle chapter 14. This is preferred form,
according to it...
WBR, Sergei
next prev parent reply other threads:[~2010-10-10 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 6:32 [PATCH 0/3] opticon driver fixes Alon Ziv
2010-10-10 6:32 ` [PATCH 1/3] Fix long-standing bugs in opticon driver Alon Ziv
2010-10-10 6:32 ` [PATCH 2/3] Add Opticon OPN2001 write support Alon Ziv
2010-10-10 10:53 ` Sergei Shtylyov
2010-10-10 12:34 ` Greg KH
2010-10-10 13:58 ` Sergei Shtylyov [this message]
2010-10-10 14:52 ` Greg KH
2010-10-10 6:32 ` [PATCH 3/3] Whitespace fixes in opticon driver Alon Ziv
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=4CB1C68F.1080905@mvista.com \
--to=sshtylyov@mvista.com \
--cc=alon+git@nolaviz.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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