From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux cdc-acm-driver
Date: Tue, 6 Mar 2012 05:54:54 -0800 [thread overview]
Message-ID: <20120306135454.GA22523@kroah.com> (raw)
In-Reply-To: <CAKgFHEr8f1OQdXO1RJpAChhRr4UU91RRWnWQKske99XXign7_A@mail.gmail.com>
On Tue, Mar 06, 2012 at 11:30:33AM +0400, tamerlan311 wrote:
> 2012/3/6 Greg KH <gregkh@linuxfoundation.org>
>
> On Mon, Mar 05, 2012 at 03:24:17PM +0400, tamerlan311 wrote:
> > This kernel module was completely stable.
> > But i think that i should do some clean up code before upstream it.
>
> There's no need to do that now, you can always send follow-on patches
> doing that.
>
> Ok.
> ?
>
>
> > Was planned for future developments:
> > implement write to device support. (I do not know why, but this feature
> was
> > implemented in original source)
>
> How can a barcode scanner be written to?
>
> Official service software can configure scanner via Bi-Directional port mode.
> Instead of special barcode for config.
>
>
>
> > implement work in UNI-Directional mode (0c2e:0710)
> >
> > I am busy working, but I'll try to finish in few week.
>
> How about I take what you have now, that ensures we make the 3.4 kernel
> release deadline, and then you send follow-on patches for the other
> things as you work on them? ?That way people can use the driver now,
> which is what they want to do :)
>
>
> I do not mind, it's a great idea!
> still need some kind of reaction from me at now?
No, I can take the code as-is and create a patch and add it to the tree
if you don't want to do that. I'll try to do it by the end of this week
and I'll cc: you on the patch.
thanks,
greg k-h
next prev parent reply other threads:[~2012-03-06 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F4A51BD.1010706@ddnetservice.net>
[not found] ` <20120229145810.GB23624@localhost>
2012-03-01 5:52 ` Linux cdc-acm-driver Manavendra Nath Manav
[not found] ` <4F4F32F2.40308@ddnetservice.net>
[not found] ` <CAJKgH8DhgY2zQ_6YLLKmJ2sCe7N9q+NukQFaASe1XVRAP6un5g@mail.gmail.com>
2012-03-01 10:18 ` Manavendra Nath Manav
2012-03-02 0:29 ` Greg KH
[not found] ` <CAKgFHEqCsBZEFxTMoCjwWoqpUicCxO722kanid21fNz=E0Kg7A@mail.gmail.com>
2012-03-05 22:29 ` Greg KH
[not found] ` <CAKgFHEr8f1OQdXO1RJpAChhRr4UU91RRWnWQKske99XXign7_A@mail.gmail.com>
2012-03-06 13:54 ` Greg KH [this message]
2012-03-01 12:18 ` Manavendra Nath Manav
2012-03-01 13:57 ` Manavendra Nath Manav
[not found] ` <4F4F85E9.3040606@ddnetservice.net>
2012-03-02 9:05 ` Manavendra Nath Manav
[not found] ` <4F5090F2.8070409@ddnetservice.net>
2012-03-02 10:36 ` Manavendra Nath Manav
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=20120306135454.GA22523@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).