linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Joy Zou <joy.zou@nxp.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"S.J. Wang" <shengjiu.wang@nxp.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH V4 2/4] dmaengine: imx-sdma: support hdmi audio
Date: Mon, 5 Sep 2022 16:33:23 +0530	[thread overview]
Message-ID: <YxXXex775kSSmGin@matsya> (raw)
In-Reply-To: <AM6PR04MB59250C67D565B6E5E52621ACE17F9@AM6PR04MB5925.eurprd04.prod.outlook.com>

On 05-09-22, 09:07, Joy Zou wrote:
> > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > >> On 01-09-22, 10:00, Joy Zou wrote:
> > >>> Add hdmi audio support in sdma.
> > >>
> > >> Pls make sure you thread your patches properly! They are broken threads!
> > > I am trying to support for hdmi audio feature on community driver
> > drivers/gpu/drm/bridge/synopsys/.
> > 
> > This does not answer to the problem you patches do not compose proper
> > thread. v5 which you sent now is also broken. Supporting HDMI audio feature
> > does not prevent you to send patches correctly, right?
> I am trying to support for hdmi audio feature on community driver drivers/gpu/drm/bridge/synopsys/.
> I think the feature may take some time because I am not audio driver owner. I only want to update the others patch as soon as possible, so I send the patch v5. I am also solving the thread patches properly.

Sorry you have not!

In my inbox, v5 1/2 and 2/2 do not appear as a single thread

Please fix the way you send the series and send them together, it is
very difficult to review when they are disjoint

FWIW, I checked the v5 2/2 and it does not have in-reply-to set, which
should point to 1/2.. If you are using git send-email, point both the
patches to it so that it will do that correctly for you

-- 
~Vinod

  reply	other threads:[~2022-09-05 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  2:00 [PATCH V4 2/4] dmaengine: imx-sdma: support hdmi audio Joy Zou
2022-09-04 16:16 ` Vinod Koul
2022-09-05  7:01   ` [EXT] " Joy Zou
2022-09-05  8:54     ` Krzysztof Kozlowski
2022-09-05  9:07       ` Joy Zou
2022-09-05 11:03         ` Vinod Koul [this message]
2022-09-06  5:04           ` Joy Zou
2022-09-06  5:16             ` Vinod Koul
2022-09-06  5:24               ` Joy Zou

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=YxXXex775kSSmGin@matsya \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=joy.zou@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=shengjiu.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).