mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
To: "Alvin Šipraga" <alvin@pqrs.dk>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Robert Foss <robert.foss@linaro.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Archit Taneja <architt@codeaurora.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] drm: bridge: adv7511: two fixes for CEC
Date: Sat, 19 Mar 2022 15:05:09 +0000	[thread overview]
Message-ID: <87r16y56fu.fsf@bang-olufsen.dk> (raw)
In-Reply-To: <20220319145939.978087-1-alvin@pqrs.dk> ("Alvin =?utf-8?Q?=C5=A0ipraga=22's?=  message of "Sat, 19 Mar 2022 15:59:37 +0100")

Alvin Šipraga <alvin@pqrs.dk> writes:

> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> The patches are sent against drm-misc-next. Thanks!

Whoops, I meant drm-misc-fixes, since these are fixes. :-)

Separate patches aimed at drm-misc-next incoming.

>
> Alvin Šipraga (2):
>   drm: bridge: adv7511: fix CEC power down control register offset
>   drm: bridge: adv7511: unregister cec i2c device after cec adapter
>
>  drivers/gpu/drm/bridge/adv7511/adv7511.h     | 5 +----
>  drivers/gpu/drm/bridge/adv7511/adv7511_cec.c | 4 ++--
>  drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 5 ++---
>  3 files changed, 5 insertions(+), 9 deletions(-)

      parent reply	other threads:[~2022-03-19 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 14:59 Alvin Šipraga
2022-03-19 14:59 ` [PATCH 1/2] drm: bridge: adv7511: fix CEC power down control register offset Alvin Šipraga
2022-03-19 14:59 ` [PATCH 2/2] drm: bridge: adv7511: unregister cec i2c device after cec adapter Alvin Šipraga
2022-03-19 15:05 ` Alvin Šipraga [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=87r16y56fu.fsf@bang-olufsen.dk \
    --to=alsi@bang-olufsen.dk \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=alvin@pqrs.dk \
    --cc=andrzej.hajda@intel.com \
    --cc=architt@codeaurora.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=robert.foss@linaro.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®