Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 28 Jul 2020 10:18:42 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Samuel Thibault <samuel.thibault@ens-lyon.org>,
        speakup@braille.uwo.ca, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/speakup: Update TODO list
Message-ID: <20200728081842.GA1648133@kroah.com>
References: <20200726165452.qhos3wrjcm6jmcmx@function>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200726165452.qhos3wrjcm6jmcmx@function>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Jul 26, 2020 at 06:54:52PM +0200, Samuel Thibault wrote:
> Thanks to Okash's latest work, the TODO list is essentially empty, so
> the way out from staging now seems open.
> 
> The status of the remaining issue mentioned in TODO is not clear, we
> asked the speakup user mailing list for reproducer cases, but didn't get
> a really specific scenario. One serious bug was fixed by 9d32c0cde4e2
> ("staging/speakup: fix get_word non-space look-ahead"), which does not
> seem to really be related to the bug mentioned in TODO. Possibly the bug
> mentioned in TODO has been fixed long ago and people have been thinking
> that it was not because they can not distinguish the symptoms mentioned
> in TODO from the symptoms of the bug fixed by 9d32c0cde4e2.

I think it's time we move speakup out of staging.  Care to submit a
patch series that does this?

thanks,

greg k-h