public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Xin Ji <xji@analogixsemi.com>
Cc: devel@driverdev.osuosl.org, drinkcat@google.com,
	span@analogixsemi.com, sam@ravnborg.org, jonas@kwiboo.se,
	airlied@linux.ie, robert.foss@linaro.org,
	narmstrong@baylibre.com, zhenli@analogixsemi.com,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	anarsoul@gmail.com, a.hajda@samsung.com,
	boris.brezillon@collabora.com, duwe@lst.de,
	Laurent.pinchart@ideasonboard.com, daniel@ffwll.ch,
	hsinyi@chromium.org, bliang@analogixsemi.com,
	m.szyprowski@samsung.com
Subject: Re: [PATCH v11 4/4] drm/bridge: anx7625: add HDMI audio function
Date: Wed, 3 Nov 2021 17:20:03 +0300	[thread overview]
Message-ID: <20211103142003.GW2794@kadam> (raw)
In-Reply-To: <20211018030529.2055255-1-xji@analogixsemi.com>

This is a super awkward way to resend a patch series.  Next time, just
start a new thread and put [PATCH RESEND] in the subject.

I am sorry that no one responded to your thread.  :/

regards,
dan carpenter

  reply	other threads:[~2021-11-03 14:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 11:07 [PATCH v11 0/4] Add MIPI rx DPI support Xin Ji
2021-08-05 11:08 ` [PATCH v11 1/4] dt-bindings:drm/bridge:anx7625:add vendor define Xin Ji
2021-10-18  3:03   ` Xin Ji
2021-10-26 23:36     ` Rob Herring
2021-08-05 11:09 ` [PATCH v11 2/4] drm/bridge: anx7625: fix not correct return value Xin Ji
2021-10-18  3:04   ` Xin Ji
2021-08-05 11:09 ` [PATCH v11 3/4] drm/bridge: anx7625: add MIPI DPI input feature Xin Ji
2021-10-18  3:04   ` Xin Ji
2021-08-05 11:10 ` [PATCH v11 4/4] drm/bridge: anx7625: add HDMI audio function Xin Ji
2021-10-18  3:05   ` Xin Ji
2021-11-03 14:20     ` Dan Carpenter [this message]
2021-11-03 15:04       ` Robert Foss
2021-11-04  0:57         ` Xin Ji
2021-11-04  0:51       ` Xin Ji
2021-10-18  3:02 ` [PATCH v11 0/4] Add MIPI rx DPI support Xin Ji

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=20211103142003.GW2794@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=anarsoul@gmail.com \
    --cc=bliang@analogixsemi.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=drinkcat@google.com \
    --cc=duwe@lst.de \
    --cc=hsinyi@chromium.org \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=narmstrong@baylibre.com \
    --cc=robert.foss@linaro.org \
    --cc=sam@ravnborg.org \
    --cc=span@analogixsemi.com \
    --cc=xji@analogixsemi.com \
    --cc=zhenli@analogixsemi.com \
    /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