From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@linux-speakup.org
Subject: Fwd: Re: speakup issues
Date: Thu, 9 May 2013 18:51:12 -0500 [thread overview]
Message-ID: <20130509235112.GD2123@linux1> (raw)
----- Forwarded message from Greg KH <gregkh@linuxfoundation.org> -----
> Date: Thu, 9 May 2013 13:47:19 -0700
> From: Greg KH <gregkh@linuxfoundation.org>
> To: William Hubbs <w.d.hubbs@gmail.com>
> Cc: devel@driverdev.osuosl.org
> Subject: Re: speakup issues
>
> On Thu, May 09, 2013 at 10:59:58AM -0500, William Hubbs wrote:
> > Hi Greg,
>
> Hi. Note my email change, you probably got the bounce from the old
> suse.de address already...
>
> > I am writing to you and to this list because I'm not quite sure where
> > else to write to ask this.
> >
> > For those on the list who do not know me, I am one of the developers
> > working on Speakup.
> >
> > I am interested in collecting a list of things that would need to happen
> > to allow speakup to move from staging to mainline. Is this list the
> > place to get that kind of information?
> >
> > Greg, if you decide when things can move, can you give me a list of
> > things that we need to look into fixing?
> >
> > I'm sure the speakup serial i/o code is one of those things, but what
> > else needs to be done?
>
> Dan has given you a great list of things to work on, start with that.
>
> Running checkpatch.pl is a great place to start with. The serial stuff
> can be worked on as well, there are better ways to resolve that problem.
>
> Also, please remove all the BUG_ON() instances, no driver should ever be
> able to instantly stop a machine, with no chance of it to be revived,
> that's just not nice.
>
> thanks,
>
> greg k-h
----- End forwarded message -----
next reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs [this message]
` covici
` Jason White
-- strict thread matches above, loose matches on Subject: below --
William Hubbs
William Hubbs
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=20130509235112.GD2123@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@linux-speakup.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 read-only IMAP folder(s) and NNTP newsgroup(s).