Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1067737imu; Fri, 7 Dec 2018 13:37:24 -0800 (PST) X-Google-Smtp-Source: AFSGD/UOKc9xSVnjnNtCkAzZMZML7GuxUrOZB9BZGdSLyHjoZgfWkmQ4j1w6ucU1zhZWwL2l3MBF X-Received: by 2002:a65:5286:: with SMTP id y6mr3373632pgp.439.1544218644013; Fri, 07 Dec 2018 13:37:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544218643; cv=none; d=google.com; s=arc-20160816; b=Te2ZA016tC9PwZvWC9kR4XiRGFv3o1fjLiMot4hhdgmZqIgdlMxo1D9GIUTgA1n+7w BweQWlMiPkAfx/58JJtUNBUxWuxYbLIhY9QOVA6Llas9GfAYzuHtqkdrPFsIiUF6jRee IZZT5ozJ+mywUverTX5Wp1bXwqd0u3p4EFQTRWU9pEbkHoHZy97FIpSaYikMiiXmnR/O XarKc3+qYejsjcOvpbImDClFfzrY0KRG3abU1I+vEftU3MD0sGVlRFP41fb9kxrSGlQA N/hriqsHX9mHlUdQVy69UNpIzkS7EsHePnbrVKCopVWatqF4Wwy4TJ6VYq7Pw/gCcTtL fTOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=dP+i4G2wSzRAn0QgynKJSJkIw51tiH0ggqE8uIpfmzY=; b=rlWzzxRX3MFdYCyt95NhjMViyLsQ6wKijq5MsovnIa/WKFVzsEaxktGQ7nKMVhKRiy OeSMaTNaDitSHc3hdW86MCgkZ0rcSP0EgPH0tsHtxI+QXgctxXaA8vGtJPLssKd3HDMg RGJeweRFh7Qb3gP+sV45nc90wSxyIYAVz/8fLGGOBh2Cg2gz9KY78H8bakgaLAOrLNKW C1VJZnTwfIWupo7JlNPkCTa7PWgbX5eC+coPM7WZbB0KYv23VH0wejd6/d2LXTPEqpHK pmPUSPXs/JE98Y+FTXQCUNz/zoQHN0lVlpLDS4dx/HCg5X13pa2LQmNRaMwDA3rY9z1v gD7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=BXY6nPQ2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y17si3928457pgh.353.2018.12.07.13.37.06; Fri, 07 Dec 2018 13:37:23 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=BXY6nPQ2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726095AbeLGVgQ (ORCPT + 99 others); Fri, 7 Dec 2018 16:36:16 -0500 Received: from mail-vk1-f193.google.com ([209.85.221.193]:38856 "EHLO mail-vk1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726008AbeLGVgQ (ORCPT ); Fri, 7 Dec 2018 16:36:16 -0500 Received: by mail-vk1-f193.google.com with SMTP id w72so1279662vkd.5 for ; Fri, 07 Dec 2018 13:36:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dP+i4G2wSzRAn0QgynKJSJkIw51tiH0ggqE8uIpfmzY=; b=BXY6nPQ2/wY0SlFiNMyIpAa/VzIcmEV7+Z0BnNxPYXewcbCncx9dbM3lhxVdRnyAJN z38wBH+gAV8AEVN26ZvNborHniPx7MenYSUOGkaTON/F9Vh9e81Q1s2LYnMUXsGa2Dz8 j4XO22NBMa24m0FgpoWDXwgITopTiM9ujVrB4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dP+i4G2wSzRAn0QgynKJSJkIw51tiH0ggqE8uIpfmzY=; b=UMwHOzjhcXxm9jKyYwOQ5kDIV84Lse/EqERvNNFKPybodO59hcFktllHoOrpWP0cMe Z4RNiVZGZOOmpeG9WQVKY+v3JIY1mwxygfcpIGQcpsUvoEH/TZaCopf6UIyqpYhuBkF9 a882YJExYCddTC/fB9Pd6lm++lfwbo77BUqkk14xlyRQ73RCSQYTX+U0yKSUDETHPEvz jhNm/dCp1pOqHP1iI6S2g/FUYOk++xi8Tw07prcS0IGVcQ1/2er2Z827kcz1U4ZWEvHN wOvzJ76nQnD3RiSc6ZfmJogw7wgh1gJU3wJY1YBfy+idTwVPjFinZ7dQJQLUwHiKAkT/ A/rg== X-Gm-Message-State: AA+aEWacnEpjoszggrCVoZUuFj5pSPH1l63Pb3nPkAbz1sGQMgd56+m3 TaVILWxC9rnHg3f9BIdvheqz17J9ZYA= X-Received: by 2002:a1f:8b48:: with SMTP id n69mr1627263vkd.12.1544218574827; Fri, 07 Dec 2018 13:36:14 -0800 (PST) Received: from mail-ua1-f54.google.com (mail-ua1-f54.google.com. [209.85.222.54]) by smtp.gmail.com with ESMTPSA id k77sm1595496vkd.17.2018.12.07.13.36.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Dec 2018 13:36:14 -0800 (PST) Received: by mail-ua1-f54.google.com with SMTP id n7so1909397uao.7 for ; Fri, 07 Dec 2018 13:36:14 -0800 (PST) X-Received: by 2002:ab0:146b:: with SMTP id c40mr1644621uae.9.1544218194278; Fri, 07 Dec 2018 13:29:54 -0800 (PST) MIME-Version: 1.0 References: <20181207152917.4862-1-georgi.djakov@linaro.org> <20181207152917.4862-9-georgi.djakov@linaro.org> <20181207162733.pdd62qvqzd6xk4nr@queper01-lin> <20181207171437.qmtacurmqg53zzkl@queper01-lin> In-Reply-To: <20181207171437.qmtacurmqg53zzkl@queper01-lin> From: Doug Anderson Date: Fri, 7 Dec 2018 13:29:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v11 8/8] interconnect: sdm845: Fix build failure after cmd_db API change To: quentin.perret@arm.com Cc: Georgi Djakov , Greg Kroah-Hartman , linux-pm@vger.kernel.org, "Rafael J. Wysocki" , Rob Herring , Michael Turquette , Kevin Hilman , Vincent Guittot , Saravana Kannan , Bjorn Andersson , Amit Kucheria , seansw@qti.qualcomm.com, daidavid1@codeaurora.org, Evan Green , Mark Rutland , Lorenzo Pieralisi , abailon@baylibre.com, maxime.ripard@bootlin.com, Arnd Bergmann , Thierry Reding , ksitaraman@nvidia.com, sanjayc@nvidia.com, devicetree@vger.kernel.org, LKML , Linux ARM , linux-arm-msm , linux-tegra@vger.kernel.org, Andy Gross , Olof Johansson Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Fri, Dec 7, 2018 at 9:14 AM Quentin Perret wrote: > > On Friday 07 Dec 2018 at 18:47:22 (+0200), Georgi Djakov wrote: > > Hi Quentin, > > > > On 12/7/18 18:27, Quentin Perret wrote: > > > Hi Georgi, > > > > > > On Friday 07 Dec 2018 at 17:29:17 (+0200), Georgi Djakov wrote: > > >> Recently the cmd_db_read_aux_data() function was changed to avoid using > > >> memcpy and return a pointer instead. Update the code to the new API and > > >> fix the build failure. > > >> > > >> Fixes: ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in cmd_db_read_aux_data()") > > >> Signed-off-by: Georgi Djakov > > >> --- > > >> drivers/interconnect/qcom/sdm845.c | 26 ++++++++++++++------------ > > > > > > IIUC this file is introduced by patch 5. Should the fix be squashed > > > into patch 5 directly ? Just to keep things bisectable. > > > > The reason why i have split it as a separate change is because as a > > separate change it would be easier to review & test for the people who > > are already familiar with the rest of the series. > > > > Another minor reason is that a separate patch will also make the life a > > bit easier for some people who are back-porting this to kernels using > > the older version of the cmd_db API. > > > > The commit that changed the cmd_db API is not yet in mainline, but in > > linux-next. I am not sure what is preferred in this case? > > Not sure either but I guess that will depend who gets merged first ... > If that's the cmd_db change, then you'll need to squash your fix in > patch 5. If your series goes first, then the fix needs to be applied to > the cmb_db change. > > I personally don't mind either way as long as we don't break bisection :-) My $0.02 is that anyone downstream picking this will also be picking the cmd db change, so I'd suggest squashing as suggested by Quentin. Maybe you can do that and post a v12? Since it sounded like Greg was about ready to land [1] maybe we shouldn't wait too long till doing it? ...unfortunately I guess we need to figure out how this will actually land. Greg can't pick the series up directly since it won't compile without the cmd-db change. ...so we need to do one of the following: 1. Feed it through a tree that goes through arm-soc (Andy's tree or arm-soc directly) so you'll have commit ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in cmd_db_read_aux_data()"). 2. Greg could also merge in Andy's pull request (https://patchwork.kernel.org/patch/10710447/), but you'll get some unrelated patches too. 3. Wait until next year and we have the next -rc1 to get this merged. ...it seems like #1 would be the least painful option, but obviously others would have to be OK w/ it. [1] https://lkml.kernel.org/r/20181206145547.GA7884@kroah.com -Doug