[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0+kfDbGrcFi5TLxNNpoOM6u6KRW+PaLFNSQJ9BTxX=-w@mail.gmail.com>
Date: Sat, 7 Sep 2019 10:21:29 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Bartosz Golaszewski <bgolaszewski@...libre.com>
Cc: Sekhar Nori <nsekhar@...com>, Bartosz Golaszewski <brgl@...ev.pl>,
Kevin Hilman <khilman@...nel.org>,
David Lechner <david@...hnology.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Hans Verkuil <hans.verkuil@...co.com>
Subject: Re: [PATCH v2 0/5] ARM: make DaVinci part of the ARM v5 multiplatform build
On Wed, Aug 28, 2019 at 9:55 AM Bartosz Golaszewski
<bgolaszewski@...libre.com> wrote:
> śr., 28 sie 2019 o 09:44 Sekhar Nori <nsekhar@...com> napisał(a):
>
> Actually I tested this without the clocksource conversion and it works
> - the previous driver still selects relevant config options. But I
> think you're right - it's worth picking up all the bug fixes from this
> series and then merging the rest once dm365 issue is fixed.
I just had another look at the series and found that the driver fixes
(patches 1 and 2) are queued in linux-next, and patch 3 was merged.
If you like, I could put the remaining two patches into the arm/late branch
and send that after the media and staging trees are merged into mainline.
Arnd
Powered by blists - more mailing lists