From: Wen Xiong <wendyx@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: "Kilau, Scott" <Scott_Kilau@digi.com>,
Wen Xiong <wendyx@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ patch 6/7] drivers/serial/jsm: new serial device driver
Date: Wed, 09 Mar 2005 15:33:40 -0500 [thread overview]
Message-ID: <422F5DA4.60807@us.ltcfwd.linux.ibm.com> (raw)
In-Reply-To: <20050309195110.GA28312@kroah.com>
Greg KH wrote:
>On Wed, Mar 09, 2005 at 01:35:41PM -0600, Kilau, Scott wrote:
>
>
>>As it stands today, your requirement appears to be that she needs
>>to yank all diags ioctls and sysfs files before the driver can make
>>it into the kernel sources.
>>
>>
>
>Not all sysfs files, sysfs files are fine, as long as they are
>implemented properly, and are there for things that "make sense".
>
>But yes, it should would be easier to accept the driver if the ioctls
>were not there :)
>
>thanks,
>
>greg k-h
>
>
>
Hi All,
I think Digi's DPA magagement tool has very good user interfaces. I am
going to change and fix the problem.
Then Greg can decide if he want to pick it up or not.
I will attatch the DPA graphic interface for you next time.
Thanks,
wendy
next prev parent reply other threads:[~2005-03-09 21:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 19:35 [ patch 6/7] drivers/serial/jsm: new serial device driver Kilau, Scott
2005-03-09 19:51 ` Greg KH
2005-03-09 20:33 ` Wen Xiong [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 17:42 Kilau, Scott
2005-03-09 19:12 ` Greg KH
2005-03-09 22:11 ` Wen Xiong
2005-02-27 23:40 Wen Xiong
2005-02-28 0:47 ` Jeff Garzik
2005-02-28 3:22 ` Christoph Hellwig
2005-02-28 0:56 ` Rik van Riel
2005-02-28 1:45 ` Nish Aravamudan
2005-02-28 6:55 ` Greg KH
2005-03-04 21:08 ` Wen Xiong
2005-03-05 6:44 ` Greg KH
2005-03-07 22:48 ` Wen Xiong
2005-03-08 6:42 ` Greg KH
2005-03-08 18:42 ` Wen Xiong
2005-03-09 6:04 ` Greg KH
2005-03-09 15:50 ` Wen Xiong
2005-03-09 16:31 ` Greg KH
2005-03-09 17:31 ` Wen Xiong
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=422F5DA4.60807@us.ltcfwd.linux.ibm.com \
--to=wendyx@us.ibm.com \
--cc=Scott_Kilau@digi.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.