Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: linux-next: build failure after merge of the sound-asoc tree
To:     Mark Brown <broonie@kernel.org>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Liam Girdwood <lgirdwood@gmail.com>,
        Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Akshu Agrawal <akshu.agrawal@amd.com>,
        Alex Deucher <alexander.deucher@amd.com>
References: <20180321133040.6754c372@canb.auug.org.au>
 <20180321024556.GX2186@sirena.org.uk>
 <3bc6e9ca-b1d9-3458-6399-758be07fd7f3@amd.com>
 <20180322013817.GY2186@sirena.org.uk>
 <3d47f2cb-0a73-98a7-bb3a-f40baf00123b@amd.com>
 <20180327112738.GA29239@sirena.org.uk>
From:   "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Message-ID: <1173f854-804a-0346-1f56-0999c5ce9f58@amd.com>
Date:   Tue, 27 Mar 2018 18:15:52 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180327112738.GA29239@sirena.org.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Received-SPF: None (protection.outlook.com: amd.com does not designate
 permitted sender hosts)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Mar 2018 12:44:14.2302 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 1b15e588-025f-473e-c729-08d593e073ae
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR12MB0309
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


On Tuesday 27 March 2018 04:57 PM, Mark Brown wrote:
> On Thu, Mar 22, 2018 at 11:24:43AM +0530, Mukunda,Vijendar wrote:
>> On Thursday 22 March 2018 07:08 AM, Mark Brown wrote:
> 
>>> You need to mention dependencies between patches when publishing and I
>>> don't seem to have a copy of that patch, according to the list archives
>>> Alex asked you to make some chnages to it.
> 
>>  ?? Changes suggested by Alex already implemented and posted .
>>  ?? Current patch (https://patchwork.kernel.org/patch/10298281/ ) is
>>  ?? dependent on below patch.
> 
>>  ?? https://patchwork.kernel.org/patch/10296597/
> 
> I'm working offline so these links aren't doing anything useful for me,
> sorry.

submitted fresh patch set which includes dependent patch.
Please ignore this mail thread.
> 
>>  ?? We will publish patch dependencies while sending patches.
> 
> Please.
>