On Thu, 2019-03-07 at 10:48 -0500, Bruce Ashfield wrote:
> On Thu, Mar 7, 2019 at 8:04 AM Richard Purdie
> wrote:
> > On Wed, 2019-03-06 at 23:23 -0500, Bruce Ashfield wrote:
> > Thanks for the other fixes, they improve things a lot. This brings
> > us
> > down to the above perf issue with 4.19
On Thu, Mar 7, 2019 at 8:04 AM Richard Purdie
wrote:
>
> On Wed, 2019-03-06 at 23:23 -0500, Bruce Ashfield wrote:
> > On Wed, Mar 6, 2019 at 11:21 PM Bruce Ashfield <
> > bruce.ashfi...@gmail.com> wrote:
> > > On Wed, Mar 6, 2019 at 6:05 PM Richard Purdie
> > > wrote:
> > > >
On Wed, 2019-03-06 at 23:23 -0500, Bruce Ashfield wrote:
> On Wed, Mar 6, 2019 at 11:21 PM Bruce Ashfield <
> bruce.ashfi...@gmail.com> wrote:
> > On Wed, Mar 6, 2019 at 6:05 PM Richard Purdie
> > wrote:
> > >
On Wed, Mar 6, 2019 at 11:21 PM Bruce Ashfield wrote:
>
> On Wed, Mar 6, 2019 at 6:05 PM Richard Purdie
> wrote:
> >
> > On Wed, 2019-03-06 at 11:37 -0500, bruce.ashfi...@gmail.com wrote:
> > > The -rc8 of the kernel pushed this out a week longer than I would
> > > have liked, but luckily the
On Wed, Mar 6, 2019 at 6:05 PM Richard Purdie
wrote:
>
> On Wed, 2019-03-06 at 11:37 -0500, bruce.ashfi...@gmail.com wrote:
> > The -rc8 of the kernel pushed this out a week longer than I would
> > have liked, but luckily the -dev kernel has been running 5.0 for
> > quite a while, so most of the
On Wed, 2019-03-06 at 11:37 -0500, bruce.ashfi...@gmail.com wrote:
> The -rc8 of the kernel pushed this out a week longer than I would
> have liked, but luckily the -dev kernel has been running 5.0 for
> quite a while, so most of the issues had been worked out already.
>
> In this series we have
