On Tue, Feb 13, 2024 at 04:40:19PM +0200, Jani Nikula wrote:
> On Tue, 13 Feb 2024, Maxime Ripard wrote:
> > On Mon, Feb 12, 2024 at 12:53:05PM +0200, Jani Nikula wrote:
> >> On Mon, 12 Feb 2024, Thomas Hellström
> >> wrote:
> >> > The indicated commit below added a device argument to the
> >> >
On Tue, 13 Feb 2024, Maxime Ripard wrote:
> On Mon, Feb 12, 2024 at 12:53:05PM +0200, Jani Nikula wrote:
>> On Mon, 12 Feb 2024, Thomas Hellström
>> wrote:
>> > The indicated commit below added a device argument to the
>> > function, but there was a call in the xe driver that was
>> > not proper
On Mon, Feb 12, 2024 at 12:53:05PM +0200, Jani Nikula wrote:
> On Mon, 12 Feb 2024, Thomas Hellström
> wrote:
> > The indicated commit below added a device argument to the
> > function, but there was a call in the xe driver that was
> > not properly changed.
>
> Aww, crap. Looks like my drm-misc
On Mon, 12 Feb 2024, Thomas Hellström wrote:
> The indicated commit below added a device argument to the
> function, but there was a call in the xe driver that was
> not properly changed.
Aww, crap. Looks like my drm-misc-next configs don't have xe enabled.
Reviewed-by: Jani Nikula
> Fixes: 5e
On Mon, Feb 12, 2024 at 11:38:33AM +0100, Thomas Hellström wrote:
> The indicated commit below added a device argument to the
> function, but there was a call in the xe driver that was
> not properly changed.
>
> Fixes: 5e0c04c8c40b ("drm/print: make drm_err_printer() device specific by
> using d
