All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Deucher, Alexander" <Alexander.Deucher@amd.com>
To: 'Mark Brown' <broonie@kernel.org>, Eric Anholt <eric@anholt.net>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	rajeev kumar <rajeevkumar.linux@gmail.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	"Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
	"perex@perex.cz" <perex@perex.cz>
Subject: RE: [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs
Date: Wed, 30 Aug 2017 21:40:07 +0000	[thread overview]
Message-ID: <BN6PR12MB16524B7C3F9BC4CA56552828F79C0@BN6PR12MB1652.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20170830211003.3qyilnuylzwjeium@sirena.org.uk>

> -----Original Message-----
> From: Mark Brown [mailto:broonie@kernel.org]
> Sent: Wednesday, August 30, 2017 5:10 PM
> To: Eric Anholt
> Cc: Alex Deucher; alsa-devel@alsa-project.org; Liam Girdwood; Maling list -
> DRI developers; rajeev kumar; amd-gfx list; Mukunda, Vijendar; Deucher,
> Alexander; perex@perex.cz
> Subject: Re: [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs
> 
> On Wed, Aug 30, 2017 at 11:49:02AM -0700, Eric Anholt wrote:
> > Mark Brown <broonie@kernel.org> writes:
> 
> > > You need to get someone from the DRM side to pay attention to the
> second
> > > patch and you need to stop resending the first patch since as has been
> > > pointed out a few times now you need to stop sending the first patch
> > > which is already in Linus' tree.
> 
> > Alex *is* from the DRM side and has reviewed that patch.
> 
> *sigh*  Right, OK in that case it would have been really helpful to see
> either some mention of this either in text or via a pull request (which
> would show the patch having been applied).  It's difficult to keep track
> of all the different people who might be DRM maintainers especially when
> there's process things like the resend of the patch from Linus' tree
> going on.

I sent one patch in the v2 patch set that had already gone upstream because I didn't know that it had landed in Linus' tree yet.  I had thought it had just landed in the audio tree.  I apologize for that.  On the v3 cover page, I mentioned that v3 was a resend of the patches that had not been applied to any tree yet; I did not resend any patches that were already applied.  I believe all the previous comments were addressed.  Now that we've clarified that, are there an outstanding objections to these patches?  The patches touch both drm and audio.  My preference would be to take them through the drm tree, but I'm happy to have them go through the audio tree if you prefer.

Thanks,

Alex

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-08-30 21:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 18:10 [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs Alex Deucher
2017-08-18 18:10 ` [PATCH 1/6 v3] drm/amd/amdgpu: Added asic_type as ACP DMA driver platform data Alex Deucher
2017-08-18 18:10 ` [PATCH 2/6 v2] drm/amdgpu Moving amdgpu asic types to a separate file Alex Deucher
     [not found] ` <1503079830-16072-1-git-send-email-alexander.deucher-5C7GfCeVMHo@public.gmane.org>
2017-08-18 18:10   ` [PATCH 3/6 v3] ASoC: AMD: disabling memory gating in stoney platform Alex Deucher
2017-08-31 11:39     ` Mark Brown
2017-08-18 18:10   ` [PATCH 4/6 v2] ASoC: AMD: DMA driver changes for Stoney Platform Alex Deucher
2017-08-31 11:39     ` Mark Brown
2017-08-18 18:10   ` [PATCH 5/6 v3] ASoC: AMD: Audio buffer related changes for Stoney Alex Deucher
2017-08-31 11:27     ` Mark Brown
2017-08-18 18:10   ` [PATCH 6/6 v3] ASoC: AMD: Add machine driver for cz rt5650 Alex Deucher
2017-08-31 11:38     ` Mark Brown
2017-09-01 11:08       ` Agrawal, Akshu
2017-08-30 13:33   ` [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs Alex Deucher
2017-08-30 15:19     ` Mark Brown
     [not found]       ` <20170830151913.6vknazyhh4se5524-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-08-30 15:46         ` Deucher, Alexander
2017-08-30 18:49       ` Eric Anholt
2017-08-30 21:10         ` Mark Brown
2017-08-30 21:40           ` Deucher, Alexander [this message]
2017-08-31 10:28             ` Mark Brown

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=BN6PR12MB16524B7C3F9BC4CA56552828F79C0@BN6PR12MB1652.namprd12.prod.outlook.com \
    --to=alexander.deucher@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=lgirdwood@gmail.com \
    --cc=perex@perex.cz \
    --cc=rajeevkumar.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.