From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752756AbdHJP0i (ORCPT ); Thu, 10 Aug 2017 11:26:38 -0400 Received: from mail-io0-f196.google.com ([209.85.223.196]:37509 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752059AbdHJP0g (ORCPT ); Thu, 10 Aug 2017 11:26:36 -0400 MIME-Version: 1.0 In-Reply-To: <20170810152010.hl2ea5tuyo7mhndf@sirena.org.uk> References: <1501776020-3328-1-git-send-email-bhumirks@gmail.com> <1501776020-3328-2-git-send-email-bhumirks@gmail.com> <20170810152010.hl2ea5tuyo7mhndf@sirena.org.uk> From: Bhumika Goyal Date: Thu, 10 Aug 2017 20:56:35 +0530 Message-ID: Subject: Re: [PATCH 1/2] ASoC: codecs: add const to snd_soc_codec_driver structures To: Mark Brown Cc: Julia Lawall , Liam Girdwood , perex@perex.cz, tiwai@suse.com, maxime.ripard@free-electrons.com, Chen-Yu Tsai , alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Lars-Peter Clausen , brian.austin@cirrus.com, Paul.Handrigan@cirrus.com, support.opensource@diasemi.com, Muthumula Jaya , vishwas.a.deshpande@ti.com, peda@axentia.se, bardliao@realtek.com, baohua@kernel.org, peter.ujfalusi@ti.com, patches@opensource.cirrus.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 10, 2017 at 8:50 PM, Mark Brown wrote: > On Thu, Aug 03, 2017 at 09:30:19PM +0530, Bhumika Goyal wrote: > >> sound/soc/codecs/88pm860x-codec.c | 2 +- >> sound/soc/codecs/ab8500-codec.c | 2 +- >> sound/soc/codecs/ac97.c | 2 +- >> sound/soc/codecs/ad1836.c | 2 +- >> sound/soc/codecs/ad193x.c | 2 +- >> sound/soc/codecs/ad1980.c | 2 +- >> sound/soc/codecs/ad73311.c | 2 +- >> sound/soc/codecs/adau1373.c | 2 +- >> sound/soc/codecs/adau1701.c | 2 +- > > This is difficult to apply against current code as it is a single commit > over lots of files but the ASoC tree has lots of branches. I've figured > out the dependencies but it's easier to split things up (and avoids > collisions with other changes causing the whole thing to not apply). Thanks for the response. Should I make separate patches for each file or is there another way to split this patch? Thanks, Bhumika