devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Robert Foss <robert.foss@linaro.org>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
	Rob Herring <robh+dt@kernel.org>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-amarula@amarulasolutions.com,
	Christopher Vollo <chris@renewoutreach.org>
Subject: Re: [PATCH v3 2/2] drm: bridge: Add TI DLPC3433 DSI to DMD bridge
Date: Mon, 13 Jun 2022 08:54:40 +0200	[thread overview]
Message-ID: <20220613065440.2vjccaixikrayvhy@pengutronix.de> (raw)
In-Reply-To: <CAG3jFyt3TwirBUbf+Zu0xuc7z+CBV8nqin0SVxVzZ7_2Qwx-vg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

Hello,

On Fri, Jun 03, 2022 at 04:37:51PM +0200, Robert Foss wrote:
> On Fri, 3 Jun 2022 at 16:04, Jagan Teki <jagan@amarulasolutions.com> wrote:
> > +static int dlpc3433_remove(struct i2c_client *client)
> > +{
> > +       struct dlpc *dlpc = i2c_get_clientdata(client);
> > +
> > +       drm_bridge_remove(&dlpc->bridge);
> > +       of_node_put(dlpc->host_node);
> > +
> > +       return 0;
> > +}
> > + [...]
> > +static struct i2c_driver dlpc3433_driver = {
> > +       .probe_new = dlpc3433_probe,
> > +       .remove = dlpc3433_remove,
> > +       .id_table = dlpc3433_id,
> > +       .driver = {
> > +               .name = "ti-dlpc3433",
> > +               .of_match_table = dlpc3433_match_table,
> > +       },
> > +};
> > +module_i2c_driver(dlpc3433_driver);
> 
> Applied to drm-misc-next.

just a quick note that there is an easy conflict between this patch and
my effort to make i2c remove callbacks return void. I intend to post my
series on top of v5.20-rc1, so if this patch goes in before, everything
is fine.

See
https://lore.kernel.org/linux-i2c/20220609091018.q52fhowlsdbdkct5@pengutronix.de/
for some more details.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-06-13  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 14:03 [PATCH v3 1/2] dt-bindings: display: bridge: Add TI DLPC3433 DSI to DMD Jagan Teki
2022-06-03 14:03 ` [PATCH v3 2/2] drm: bridge: Add TI DLPC3433 DSI to DMD bridge Jagan Teki
2022-06-03 14:37   ` Robert Foss
2022-06-13  6:54     ` Uwe Kleine-König [this message]

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=20220613065440.2vjccaixikrayvhy@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrzej.hajda@intel.com \
    --cc=chris@renewoutreach.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=narmstrong@baylibre.com \
    --cc=robert.foss@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).