* linux-next: build failure after merge of the drm tree
@ 2021-01-08 0:55 Stephen Rothwell
2021-01-08 1:25 ` Stephen Rothwell
0 siblings, 1 reply; 11+ messages in thread
From: Stephen Rothwell @ 2021-01-08 0:55 UTC (permalink / raw)
To: Dave Airlie, DRI
Cc: Sebastian Reichel, Tomi Valkeinen, Linux Kernel Mailing List,
Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
Hi all,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
error: the following would cause module name conflict:
drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko
drivers/gpu/drm/panel/panel-dsi-cm.ko
Maybe caused by commit
cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver")
I have used the drm tree from next-20210107 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: linux-next: build failure after merge of the drm tree 2021-01-08 0:55 linux-next: build failure after merge of the drm tree Stephen Rothwell @ 2021-01-08 1:25 ` Stephen Rothwell 2021-01-08 11:24 ` [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Sebastian Reichel 2021-01-10 23:56 ` linux-next: build failure after merge of the drm tree Stephen Rothwell 0 siblings, 2 replies; 11+ messages in thread From: Stephen Rothwell @ 2021-01-08 1:25 UTC (permalink / raw) To: Daniel Vetter, Intel Graphics Cc: Dave Airlie, DRI, Sebastian Reichel, Tomi Valkeinen, Linux Kernel Mailing List, Linux Next Mailing List [-- Attachment #1: Type: text/plain, Size: 727 bytes --] Hi all, On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > Hi all, > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > error: the following would cause module name conflict: > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko > drivers/gpu/drm/panel/panel-dsi-cm.ko > > Maybe caused by commit > > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > I have used the drm tree from next-20210107 for today. This has affected the drm-misc tree as well (since it merged in the drm tree). I have used the drm-misc tree from next-20210107 for today. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive 2021-01-08 1:25 ` Stephen Rothwell @ 2021-01-08 11:24 ` Sebastian Reichel 2021-01-08 19:58 ` Sam Ravnborg 2021-01-10 23:56 ` linux-next: build failure after merge of the drm tree Stephen Rothwell 1 sibling, 1 reply; 11+ messages in thread From: Sebastian Reichel @ 2021-01-08 11:24 UTC (permalink / raw) To: Sebastian Reichel, Tomi Valkeinen, Bartlomiej Zolnierkiewicz Cc: Laurent Pinchart, Stephen Rothwell, Sam Ravnborg, dri-devel, linux-fbdev, linux-kernel, linux-next, Sebastian Reichel, kernel Standard DRM panel driver for DSI command mode panel used by omapfb2 is also available now. Just like the other panels its module name clashes with the module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver is disabled, and the DRM panel drivers are useless in that case, make the omapfb2 panel depend on the standard DRM panels being disabled to fix the name clash. Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> --- Laurent introduced and fixed the same issue for the other panels and this simply replicates the same solution for DSI command mode panel. --- drivers/video/fbdev/omap2/omapfb/displays/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig index 744416dc530e..384d74a126dc 100644 --- a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig +++ b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig @@ -43,6 +43,7 @@ config FB_OMAP2_PANEL_DPI config FB_OMAP2_PANEL_DSI_CM tristate "Generic DSI Command Mode Panel" depends on BACKLIGHT_CLASS_DEVICE + depends on DRM_PANEL_DSI_CM = n help Driver for generic DSI command mode panels. -- 2.29.2 ^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive 2021-01-08 11:24 ` [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Sebastian Reichel @ 2021-01-08 19:58 ` Sam Ravnborg 2021-01-12 12:02 ` Sebastian Reichel 0 siblings, 1 reply; 11+ messages in thread From: Sam Ravnborg @ 2021-01-08 19:58 UTC (permalink / raw) To: Sebastian Reichel Cc: Sebastian Reichel, Tomi Valkeinen, Bartlomiej Zolnierkiewicz, Laurent Pinchart, Stephen Rothwell, dri-devel, linux-fbdev, linux-kernel, linux-next, kernel Hi Sebatian, On Fri, Jan 08, 2021 at 12:24:41PM +0100, Sebastian Reichel wrote: > Standard DRM panel driver for DSI command mode panel used by omapfb2 is also > available now. Just like the other panels its module name clashes with the > module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated > omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver > is disabled, and the DRM panel drivers are useless in that case, make the > omapfb2 panel depend on the standard DRM panels being disabled to fix > the name clash. > > Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> For a backport this looks good: Acked-by: Sam Ravnborg <sam@ravnborg.org> But why is it it we need omapfb at all when we have omapdrm? Can we sunset all or some parts of omap support in video/? If not, what is missing to do so. Sam > --- > Laurent introduced and fixed the same issue for the other panels and > this simply replicates the same solution for DSI command mode panel. > --- > drivers/video/fbdev/omap2/omapfb/displays/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig > index 744416dc530e..384d74a126dc 100644 > --- a/drivers/video/fbdev/omap2/omapfb/displays/Kconfig > +++ b/drivers/video/fbdev/omap2/omapfb/displays/Kconfig > @@ -43,6 +43,7 @@ config FB_OMAP2_PANEL_DPI > config FB_OMAP2_PANEL_DSI_CM > tristate "Generic DSI Command Mode Panel" > depends on BACKLIGHT_CLASS_DEVICE > + depends on DRM_PANEL_DSI_CM = n > help > Driver for generic DSI command mode panels. > > -- > 2.29.2 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive 2021-01-08 19:58 ` Sam Ravnborg @ 2021-01-12 12:02 ` Sebastian Reichel 2021-01-12 13:10 ` Tomi Valkeinen 0 siblings, 1 reply; 11+ messages in thread From: Sebastian Reichel @ 2021-01-12 12:02 UTC (permalink / raw) To: Sam Ravnborg Cc: Tomi Valkeinen, Tomi Valkeinen, Bartlomiej Zolnierkiewicz, Laurent Pinchart, Stephen Rothwell, dri-devel, linux-fbdev, linux-kernel, linux-next, kernel [-- Attachment #1: Type: text/plain, Size: 2047 bytes --] [replace Tomi's TI mail address with something working] Hi, On Fri, Jan 08, 2021 at 08:58:39PM +0100, Sam Ravnborg wrote: > Hi Sebastian, > > On Fri, Jan 08, 2021 at 12:24:41PM +0100, Sebastian Reichel wrote: > > Standard DRM panel driver for DSI command mode panel used by omapfb2 is also > > available now. Just like the other panels its module name clashes with the > > module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated > > omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver > > is disabled, and the DRM panel drivers are useless in that case, make the > > omapfb2 panel depend on the standard DRM panels being disabled to fix > > the name clash. > > > > Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> > > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> > > For a backport this looks good: > Acked-by: Sam Ravnborg <sam@ravnborg.org> Thanks. > But why is it it we need omapfb at all when we have omapdrm? I think there are two reasons omapfb has not been killed yet. One reason was missing support for manually updated DSI panels, which have been working since 1 or 2 kernel releases now. The other reason is some people using it in combination with an out-of-tree PowerVR kernel driver. There is currently work going on to use a more recent PowerVR driver based on omapdrm driven by Maemo Leste people. > Can we sunset all or some parts of omap support in video/? > If not, what is missing to do so. IDK the exact status of the PowerVR work and have not been using omapfb myself for years. I don't think there is a reason to rush this, so my suggestion is removing it in 3 steps giving people the chance to complain: 1. Add 'depends on EXPERT' to 'FB_OMAP2' and add deprecation notice referencing omapdrm in help text in 5.12 2. Add 'depends on BROKEN' in 5.13 3. Drop drivers/video/fbdev/omap2 afterwards -- Sebastian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive 2021-01-12 12:02 ` Sebastian Reichel @ 2021-01-12 13:10 ` Tomi Valkeinen 0 siblings, 0 replies; 11+ messages in thread From: Tomi Valkeinen @ 2021-01-12 13:10 UTC (permalink / raw) To: Sebastian Reichel, Sam Ravnborg Cc: Tomi Valkeinen, Bartlomiej Zolnierkiewicz, Laurent Pinchart, Stephen Rothwell, dri-devel, linux-fbdev, linux-kernel, linux-next, kernel Hi, On 12/01/2021 14:02, Sebastian Reichel wrote: > [replace Tomi's TI mail address with something working] > > Hi, > > On Fri, Jan 08, 2021 at 08:58:39PM +0100, Sam Ravnborg wrote: >> Hi Sebastian, >> >> On Fri, Jan 08, 2021 at 12:24:41PM +0100, Sebastian Reichel wrote: >>> Standard DRM panel driver for DSI command mode panel used by omapfb2 is also >>> available now. Just like the other panels its module name clashes with the >>> module from drivers/video/fbdev/omap2/omapfb/displays, part of the deprecated >>> omapfb2 fbdev driver. As omapfb2 can only be compiled when the omapdrm driver >>> is disabled, and the DRM panel drivers are useless in that case, make the >>> omapfb2 panel depend on the standard DRM panels being disabled to fix >>> the name clash. >>> >>> Fixes: cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") >>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> >>> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> >> >> For a backport this looks good: >> Acked-by: Sam Ravnborg <sam@ravnborg.org> > > Thanks. Thanks. I'll push to drm-misc-next, as that's where the commit that breaks this is. >> But why is it it we need omapfb at all when we have omapdrm? > > I think there are two reasons omapfb has not been killed yet. One > reason was missing support for manually updated DSI panels, which > have been working since 1 or 2 kernel releases now. The other reason > is some people using it in combination with an out-of-tree PowerVR > kernel driver. There is currently work going on to use a more recent > PowerVR driver based on omapdrm driven by Maemo Leste people. omapfb also has a custom sysfw API, so applications that depend on it would not work anymore. I don't know if there are such applications, though. >> Can we sunset all or some parts of omap support in video/? >> If not, what is missing to do so. > > IDK the exact status of the PowerVR work and have not been using > omapfb myself for years. I don't think there is a reason to rush > this, so my suggestion is removing it in 3 steps giving people > the chance to complain: > > 1. Add 'depends on EXPERT' to 'FB_OMAP2' and add deprecation notice > referencing omapdrm in help text in 5.12 > 2. Add 'depends on BROKEN' in 5.13 > 3. Drop drivers/video/fbdev/omap2 afterwards I'd love to remove omapfb, but I also fear that there are still people using it. We can try the above sequence, but it's probably better to go slower, as people may not be using the latest kernels. Tomi ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: linux-next: build failure after merge of the drm tree 2021-01-08 1:25 ` Stephen Rothwell 2021-01-08 11:24 ` [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Sebastian Reichel @ 2021-01-10 23:56 ` Stephen Rothwell 2021-01-18 0:59 ` Stephen Rothwell 1 sibling, 1 reply; 11+ messages in thread From: Stephen Rothwell @ 2021-01-10 23:56 UTC (permalink / raw) To: Daniel Vetter, Intel Graphics, Jani Nikula, Joonas Lahtinen, Rodrigo Vivi Cc: Dave Airlie, DRI, Sebastian Reichel, Tomi Valkeinen, Linux Kernel Mailing List, Linux Next Mailing List [-- Attachment #1: Type: text/plain, Size: 932 bytes --] Hi all, On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > error: the following would cause module name conflict: > > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko > > drivers/gpu/drm/panel/panel-dsi-cm.ko > > > > Maybe caused by commit > > > > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > > > I have used the drm tree from next-20210107 for today. > > This has affected the drm-misc tree as well (since it merged in the drm > tree). > > I have used the drm-misc tree from next-20210107 for today. And now the drm-intel tree. I have used the drm-intel tree from next-20210108 for today. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: linux-next: build failure after merge of the drm tree 2021-01-10 23:56 ` linux-next: build failure after merge of the drm tree Stephen Rothwell @ 2021-01-18 0:59 ` Stephen Rothwell 2021-01-18 1:06 ` Dave Airlie 0 siblings, 1 reply; 11+ messages in thread From: Stephen Rothwell @ 2021-01-18 0:59 UTC (permalink / raw) To: Daniel Vetter, Intel Graphics, Jani Nikula, Joonas Lahtinen, Rodrigo Vivi Cc: Dave Airlie, DRI, Sebastian Reichel, Tomi Valkeinen, Linux Kernel Mailing List, Linux Next Mailing List [-- Attachment #1: Type: text/plain, Size: 1132 bytes --] Hi all, On Mon, 11 Jan 2021 10:56:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > > > failed like this: > > > > > > error: the following would cause module name conflict: > > > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko > > > drivers/gpu/drm/panel/panel-dsi-cm.ko > > > > > > Maybe caused by commit > > > > > > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > > > > > I have used the drm tree from next-20210107 for today. > > > > This has affected the drm-misc tree as well (since it merged in the drm > > tree). > > > > I have used the drm-misc tree from next-20210107 for today. > > And now the drm-intel tree. > > I have used the drm-intel tree from next-20210108 for today. This is still affecting the drm and drm-intel trees. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: linux-next: build failure after merge of the drm tree 2021-01-18 0:59 ` Stephen Rothwell @ 2021-01-18 1:06 ` Dave Airlie 2021-01-20 12:12 ` Daniel Vetter 0 siblings, 1 reply; 11+ messages in thread From: Dave Airlie @ 2021-01-18 1:06 UTC (permalink / raw) To: Stephen Rothwell, Maarten Lankhorst Cc: Daniel Vetter, Intel Graphics, Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Dave Airlie, Tomi Valkeinen, Sebastian Reichel, DRI, Linux Kernel Mailing List, Linux Next Mailing List On Mon, 18 Jan 2021 at 10:59, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > Hi all, > > On Mon, 11 Jan 2021 10:56:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > > > > failed like this: > > > > > > > > error: the following would cause module name conflict: > > > > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko > > > > drivers/gpu/drm/panel/panel-dsi-cm.ko > > > > > > > > Maybe caused by commit > > > > > > > > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > > > > > > > I have used the drm tree from next-20210107 for today. > > > > > > This has affected the drm-misc tree as well (since it merged in the drm > > > tree). > > > > > > I have used the drm-misc tree from next-20210107 for today. > > > > And now the drm-intel tree. > > > > I have used the drm-intel tree from next-20210108 for today. > > This is still affecting the drm and drm-intel trees. I think the fix for this is in drm-misc-next, Maarten can you send me a -next PR to fix this? Dave. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: linux-next: build failure after merge of the drm tree 2021-01-18 1:06 ` Dave Airlie @ 2021-01-20 12:12 ` Daniel Vetter 2021-01-20 20:44 ` Stephen Rothwell 0 siblings, 1 reply; 11+ messages in thread From: Daniel Vetter @ 2021-01-20 12:12 UTC (permalink / raw) To: Dave Airlie Cc: Stephen Rothwell, Maarten Lankhorst, Intel Graphics, Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Dave Airlie, Tomi Valkeinen, Sebastian Reichel, DRI, Linux Kernel Mailing List, Linux Next Mailing List On Mon, Jan 18, 2021 at 2:06 AM Dave Airlie <airlied@gmail.com> wrote: > > On Mon, 18 Jan 2021 at 10:59, Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > Hi all, > > > > On Mon, 11 Jan 2021 10:56:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > On Fri, 8 Jan 2021 12:25:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > > > On Fri, 8 Jan 2021 11:55:18 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > > > > > > > > > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > > > > > failed like this: > > > > > > > > > > error: the following would cause module name conflict: > > > > > drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.ko > > > > > drivers/gpu/drm/panel/panel-dsi-cm.ko > > > > > > > > > > Maybe caused by commit > > > > > > > > > > cf64148abcfd ("drm/panel: Move OMAP's DSI command mode panel driver") > > > > > > > > > > I have used the drm tree from next-20210107 for today. > > > > > > > > This has affected the drm-misc tree as well (since it merged in the drm > > > > tree). > > > > > > > > I have used the drm-misc tree from next-20210107 for today. > > > > > > And now the drm-intel tree. > > > > > > I have used the drm-intel tree from next-20210108 for today. > > > > This is still affecting the drm and drm-intel trees. > > I think the fix for this is in drm-misc-next, Maarten can you send me > a -next PR to fix this? I've pulled drm-misc-next into drm-next now, so as long as all other drm trees are merged after drm, this should be solved now. drm-intel-next also has their msm build breakage fixed (I acked the patch already), so hopefully we should be all clean again. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: linux-next: build failure after merge of the drm tree 2021-01-20 12:12 ` Daniel Vetter @ 2021-01-20 20:44 ` Stephen Rothwell 0 siblings, 0 replies; 11+ messages in thread From: Stephen Rothwell @ 2021-01-20 20:44 UTC (permalink / raw) To: Daniel Vetter Cc: Dave Airlie, Maarten Lankhorst, Intel Graphics, Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Dave Airlie, Tomi Valkeinen, Sebastian Reichel, DRI, Linux Kernel Mailing List, Linux Next Mailing List [-- Attachment #1: Type: text/plain, Size: 411 bytes --] Hi Daniel, On Wed, 20 Jan 2021 13:12:21 +0100 Daniel Vetter <daniel.vetter@ffwll.ch> wrote: > > I've pulled drm-misc-next into drm-next now, so as long as all other > drm trees are merged after drm, this should be solved now. > drm-intel-next also has their msm build breakage fixed (I acked the > patch already), so hopefully we should be all clean again. Thanks. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2021-01-20 20:46 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-01-08 0:55 linux-next: build failure after merge of the drm tree Stephen Rothwell 2021-01-08 1:25 ` Stephen Rothwell 2021-01-08 11:24 ` [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive Sebastian Reichel 2021-01-08 19:58 ` Sam Ravnborg 2021-01-12 12:02 ` Sebastian Reichel 2021-01-12 13:10 ` Tomi Valkeinen 2021-01-10 23:56 ` linux-next: build failure after merge of the drm tree Stephen Rothwell 2021-01-18 0:59 ` Stephen Rothwell 2021-01-18 1:06 ` Dave Airlie 2021-01-20 12:12 ` Daniel Vetter 2021-01-20 20:44 ` Stephen Rothwell
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).