mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Fabio Estevam <fabio.estevam@nxp.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	Marco Franchi <marcofrk@gmail.com>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] drm: mxsfb: Change driver.name to mxsfb-drm
Date: Fri, 15 Jun 2018 22:43:42 +0300	[thread overview]
Message-ID: <47ea7572011735b68a8a70f0e11bdf00cb2fd86a.1529091248.git.leonard.crestez@nxp.com> (raw)
In-Reply-To: <cover.1529091248.git.leonard.crestez@nxp.com>

The FBDEV driver uses the same name and both can't be registered at the
same time. Fix this by renaming the drm driver to mxsfb-drm

Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
---
 drivers/gpu/drm/mxsfb/mxsfb_drv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/mxsfb/mxsfb_drv.c b/drivers/gpu/drm/mxsfb/mxsfb_drv.c
index ffe5137ccaf8..dd1dd58e4956 100644
--- a/drivers/gpu/drm/mxsfb/mxsfb_drv.c
+++ b/drivers/gpu/drm/mxsfb/mxsfb_drv.c
@@ -417,11 +417,11 @@ static int mxsfb_remove(struct platform_device *pdev)
 static struct platform_driver mxsfb_platform_driver = {
 	.probe		= mxsfb_probe,
 	.remove		= mxsfb_remove,
 	.id_table	= mxsfb_devtype,
 	.driver	= {
-		.name		= "mxsfb",
+		.name		= "mxsfb-drm",
 		.of_match_table	= mxsfb_dt_ids,
 	},
 };
 
 module_platform_driver(mxsfb_platform_driver);
-- 
2.17.1


  reply	other threads:[~2018-06-15 19:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 19:43 [PATCH 0/3] ARM: imx: Make DRM_MXSFB and FB_MXS coexist Leonard Crestez
2018-06-15 19:43 ` Leonard Crestez [this message]
2018-06-15 19:47   ` [PATCH 1/3] drm: mxsfb: Change driver.name to mxsfb-drm Fabio Estevam
2018-06-15 20:58     ` Leonard Crestez
2018-06-15 21:05       ` Fabio Estevam
2018-06-15 21:36       ` Marek Vasut
2018-06-15 22:22         ` Fabio Estevam
2018-06-15 23:29           ` Marek Vasut
2018-06-15 22:42         ` Leonard Crestez
2018-06-15 23:32           ` Marek Vasut
2018-06-18  7:43             ` Daniel Vetter
2018-06-18  8:13               ` Stefan Agner
2018-07-10  9:06             ` Stefan Agner
2018-07-10  9:11               ` Marek Vasut
2018-07-12  9:21                 ` Stefan Agner
2018-07-12 13:03                   ` Leonard Crestez
2018-07-12 13:14                     ` Marek Vasut
2018-07-13  7:25                       ` Daniel Vetter
2018-07-12 13:46                     ` Stefan Agner
2018-07-12 12:15                 ` Stefan Agner
2018-06-15 19:43 ` [PATCH 2/3] fbdev: mxsfb: Return ENODEV on missing display node Leonard Crestez
2018-06-15 19:43 ` [PATCH 3/3] ARM: imx_v6_v7_defconfig: Enable DRM_MXSFB Leonard Crestez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47ea7572011735b68a8a70f0e11bdf00cb2fd86a.1529091248.git.leonard.crestez@nxp.com \
    --to=leonard.crestez@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcofrk@gmail.com \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®