From: Mark Brown <broonie@kernel.org>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Liam Girdwood <lgirdwood@gmail.com>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
"Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
"Zhu, Rex" <Rex.Zhu@amd.com>
Subject: Re: linux-next: manual merge of the sound-asoc tree with the drm-misc tree
Date: Wed, 18 Oct 2017 15:52:45 +0100 [thread overview]
Message-ID: <20171018145245.abldlx2e5to3gsfs@sirena.co.uk> (raw)
In-Reply-To: <BN6PR12MB16527C9DCEEA4D46EEF1AA90F74D0@BN6PR12MB1652.namprd12.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]
On Wed, Oct 18, 2017 at 02:30:50PM +0000, Deucher, Alexander wrote:
> The patch below effectively reverts 1e4448648333a. If you drop the patch below, you should be fine.
As I said in my followup mail I've dropped all these patches due to
build failures, please resend both the pull request and the patches with
any required fixups.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-10-18 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 9:57 linux-next: manual merge of the sound-asoc tree with the drm-misc tree Mark Brown
2017-10-18 10:08 ` Mark Brown
2017-10-18 14:33 ` Deucher, Alexander
2017-10-18 16:26 ` Mark Brown
2017-10-18 14:30 ` Deucher, Alexander
2017-10-18 14:52 ` Mark Brown [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=20171018145245.abldlx2e5to3gsfs@sirena.co.uk \
--to=broonie@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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