[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAG3jFys+J1389TSADvR1jYOOQXig2thftfXKtgsGZLWkwA34bg@mail.gmail.com>
Date: Mon, 28 Feb 2022 16:33:22 +0100
From: Robert Foss <robert.foss@...aro.org>
To: Dave Airlie <airlied@...il.com>
Cc: Hsin-Yi Wang <hsinyi@...omium.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Mark Brown <broonie@...nel.org>,
Dave Airlie <airlied@...ux.ie>,
Allen Chen <allen.chen@....com.tw>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hermes Wu <Hermes.Wu@....com.tw>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
DRI <dri-devel@...ts.freedesktop.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Subject: Re: linux-next: build failure after merge of the drm tree
> > >
> > > Caused by commit
> > >
> > > b5c84a9edcd418 ("drm/bridge: add it6505 driver")
> > >
> > > I have used the drm tree from yesterday instead.
> >
> > hi all,
> >
> > The following fix should be able to address the errors. Should it be
> > squashed into b5c84a9edcd418 ("drm/bridge: add it6505 driver")?
>
> Can you send a patch with this to dri-devel? It's far too far down the
> tree to sqaush anything at this point.
>
Patch submitted & reviewed.
https://lore.kernel.org/all/20220228081421.1504213-1-hsinyi@chromium.org/
Should I apply it drm-misc-next?
Powered by blists - more mailing lists