From: Vitaliy Ivanov <vitalivanov@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: zaitcev@redhat.com, gregkh@suse.de,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, vitalivanov@gmail.com
Subject: Re: [2.4 patch] Port of adutux driver from 2.6 kernel to 2.4.
Date: Tue, 16 Oct 2007 21:24:11 +0300 [thread overview]
Message-ID: <1192559051.29039.139.camel@dell1.softservecom.com> (raw)
In-Reply-To: <20071016154138.GA23326@1wt.eu>
On Tue, 2007-10-16 at 18:41, Willy Tarreau wrote:
> OK, I have no objection, but please apply the fixes the le16 problem as
> suggested by Pete and Greg first. Also, you will probably receive more
> comments, and/or criticisms from further reviews. This is normal and
> expected. You just have to fix your code so that it can be merged.
Done. Removed all le16_to_cpu's.
Comments are OK. Just a little bit busy on my regular work. So can give
responses not so quickly as you probably wanted.
> > adutux is a simple Linux device driver for ADU boards from Ontrak Control Systems.
> > The adutux driver exposes standard open/close/read/write API's to the user application.
>
> If this is going to be the commit message, please reduce lines to less
> than 70 chars, and also enumerate the supportd devices and the one you
> performed the tests with. It helps a lot when users encounter problems.
>
It's a driver description you asked for previously.
Commit message should look like this probably:
"Port of adutux driver from 2.6 kernel for Ontrak ADU boards."
Devices list:
As I said previously supported devices are:
http://www.ontrak.net/products.htm#Table%205
Just to list them here:
ADU100, ADU120, ADU130, ADU200, ADU208, ADU218.
Testing is performed on ADU200.
But command structure is identical for this devices and it is only
individual command syntax that varies between different ADU devices.
> Also, if you did not (I forgot to check), please ensure that the adutux
> maintainer in 2.6 is CC'd.
There is not maintainer for this device in 2.6.
Following Pete notes I will rework code and give it for review once again.
As I said it's usb-skeleton approach that I reused during the port.
Anyway, will get back to this soon.
Vitaliy
next prev parent reply other threads:[~2007-10-16 18:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 17:37 Vitaliy Ivanov
2007-10-14 18:25 ` Willy Tarreau
2007-10-14 20:45 ` Vitaliy Ivanov
2007-10-14 22:39 ` Willy Tarreau
2007-10-16 13:54 ` Vitaliy Ivanov
2007-10-16 15:41 ` Willy Tarreau
2007-10-16 17:56 ` Pete Zaitcev
2007-10-16 18:22 ` Vitaliy Ivanov
2007-10-16 18:24 ` Willy Tarreau
2007-10-16 18:24 ` Vitaliy Ivanov [this message]
2007-10-17 18:12 ` Vitaliy Ivanov
2007-10-19 15:26 ` Vitaliy Ivanov
2007-10-19 16:53 ` Pete Zaitcev
2007-10-19 17:40 ` Vitaliy Ivanov
2007-10-23 3:45 ` Pete Zaitcev
2007-11-04 14:05 ` Willy Tarreau
2007-11-05 9:32 ` Vitaliy Ivanov
2007-11-05 9:36 ` Willy Tarreau
2007-10-16 17:52 ` Pete Zaitcev
2007-10-15 17:30 ` Pete Zaitcev
2007-10-15 20:04 ` Vitaliy Ivanov
2007-10-16 13:48 ` Vitaliy Ivanov
2007-10-16 14:59 ` Greg KH
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=1192559051.29039.139.camel@dell1.softservecom.com \
--to=vitalivanov@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=w@1wt.eu \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®