From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Okash Khawaja <okash.khawaja@gmail.com>
Cc: devel@driverdev.osuosl.org,
Simon Dickson <simonhdickson@gmail.com>,
Gregory Nowak <greg@gregn.net>,
"Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>,
linux-kernel@vger.kernel.org, John Covici <covici@ccs.covici.com>
Subject: Re: [HELP REQUESTED from the community] Was: Staging status of speakup
Date: Sun, 15 Sep 2019 15:43:00 +0200 [thread overview]
Message-ID: <20190915134300.GA552892@kroah.com> (raw)
In-Reply-To: <CAOtcWM0P=w-iBZzwekVrSpp7t2WO9RA5WP956zgDrNKvzA+4ZA@mail.gmail.com>
On Sat, Sep 14, 2019 at 10:08:35PM +0100, Okash Khawaja wrote:
> On Mon, Sep 9, 2019 at 3:55 AM Gregory Nowak <greg@gregn.net> wrote:
> >
> > On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote:
> > > Sorry, I have only now got round to working on this. It's not complete
> > > yet but I have assimilated the feedback and converted subjective
> > > phrases, like "I think..." into objective statements or put them in
> > > TODO: so that someone else may verify. I have attached it to this
> > > email.
> >
> > I think bleeps needs a TODO, since we don't know what values it accepts, or
> > what difference those values make. Also, to keep things uniform, we
> > should replace my "don't know" for trigger_time with a TODO. Looks
> > good to me otherwise. Thanks.
>
> Great thanks. I have updated.
>
> I have two questions:
>
> 1. Is it okay for these descriptions to go inside
> Documentation/ABI/stable? They have been around since 2.6 (2010). Or
> would we prefer Documentation/ABI/testing/?
stable is fine.
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-09-15 13:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190315130035.6a8f16e9@narunkot>
[not found] ` <20190316031831.GA2499@kroah.com>
2019-07-06 19:08 ` Staging status of speakup Okash Khawaja
2019-07-07 6:57 ` Greg Kroah-Hartman
2019-07-12 8:38 ` Greg Kroah-Hartman
2019-07-12 9:23 ` [HELP REQUESTED from the community] Was: " Samuel Thibault
2019-07-13 0:46 ` Gregory Nowak
[not found] ` <20190725035352.GA7717@gregn.net>
[not found] ` <875znqhia0.fsf@cmbmachine.messageid.invalid>
[not found] ` <m3sgqucs1x.wl-covici@ccs.covici.com>
[not found] ` <CAOtcWM0qynSjnF6TtY_s7a51B7JweDb7jwdxStEmPvB9tJFU4Q@mail.gmail.com>
[not found] ` <20190821222209.GA4577@gregn.net>
2019-09-08 9:43 ` Okash Khawaja
2019-09-09 2:54 ` Gregory Nowak
2019-09-14 21:08 ` Okash Khawaja
2019-09-14 23:32 ` Samuel Thibault
2019-09-15 13:43 ` Greg Kroah-Hartman [this message]
2019-09-15 18:41 ` Okash Khawaja
2019-09-16 13:47 ` Samuel Thibault
2019-09-16 14:11 ` Greg Kroah-Hartman
2019-09-16 22:38 ` Gregory Nowak
2019-09-17 8:01 ` Greg Kroah-Hartman
2019-09-18 1:03 ` Gregory Nowak
2019-09-18 6:16 ` Greg Kroah-Hartman
2019-09-18 20:30 ` Gregory Nowak
2019-09-20 7:46 ` Greg Kroah-Hartman
2019-09-20 10:18 ` Okash Khawaja
2019-09-16 20:21 ` Gregory Nowak
2019-07-12 9:24 ` Okash Khawaja
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=20190915134300.GA552892@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=covici@ccs.covici.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@gregn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=okash.khawaja@gmail.com \
--cc=simonhdickson@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 NNTP newsgroup(s).