Received: by 10.213.65.68 with SMTP id h4csp235775imn; Fri, 16 Mar 2018 01:09:07 -0700 (PDT) X-Google-Smtp-Source: AG47ELs2N/sraWM9NHJLnD5+dcF0MMjFGK/fz2DT98Ftt4W1fk5gYI0zSYZDzzjoDImCmIorMZBT X-Received: by 2002:a17:902:24a5:: with SMTP id w34-v6mr1101284pla.328.1521187747116; Fri, 16 Mar 2018 01:09:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521187747; cv=none; d=google.com; s=arc-20160816; b=Ho8LBk/sUvwkq1bc2uuvtyO6Ok6jKXNtaOK1xkAm1YbCkb9R7PqvDc2V3Tg6bXEH13 H3EHrSfYov77Tt4T84/Hx40v7MYYAZTZdv/5Qu7KjShhgrAcwO/kaFu6jX2l9aO/IC8R Kf+K6QdhjanKWfYUxQpAUT3vqaaGQxQyC41CVEWJPBAohaE36lwb3aSw3Sa6eFfTcYpo othCGTl79KHfTQAwpNTkeWB0NMx3dqxHazsW9ZxKIFG3Fk/+8EA1+g5vFba6f1sLtzOC 077EYJ4A0UM0Ea6dQE0cB/fsz92OaQwgnYD5JQj9AxlmK6ID7sWzahlNABOuC8PFvIZy QzjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=g0qhrPaNFXprhc3cZYbGlbf//MPehpcRQRML1FYj4So=; b=kmWv4ErhRj7Qo9KmMJmaSpeMVy7sHt0U4Koc8wCVXo9Mm1blH+h7WjNnFLgzduTVu5 UEL1YG+e1VHQ4o+m06xpXcavTF16qyQ0VAJeCnZYxS6q5FgXeFJY1F8wKZBXbM6m1r1T eZuweTrNIGu3jksgJHMyTvLcEg8+zkzG+cBj9H2z1wPKJar6XV4MTlFFEYvIIHb+Jmos eoFYTqCAJAc/FymgmTAaI1ebzRrpnk7ztYsdWQWNpJYk/misSbxCm+0gHIjD8d66qQ21 ZZq5tIj4w0E2StliHBv1h1t0RWpDut8QaPeVOwxNt96z7IfZ9M32lNytcNr1WiBI1fN3 lEQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=aeNfzRe7; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h3si173792pfb.208.2018.03.16.01.08.51; Fri, 16 Mar 2018 01:09:07 -0700 (PDT) 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=fail header.i=@gmail.com header.s=20161025 header.b=aeNfzRe7; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752585AbeCPIHz (ORCPT + 99 others); Fri, 16 Mar 2018 04:07:55 -0400 Received: from mail-io0-f175.google.com ([209.85.223.175]:40741 "EHLO mail-io0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750991AbeCPIHu (ORCPT ); Fri, 16 Mar 2018 04:07:50 -0400 Received: by mail-io0-f175.google.com with SMTP id e79so3420728ioi.7; Fri, 16 Mar 2018 01:07:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=g0qhrPaNFXprhc3cZYbGlbf//MPehpcRQRML1FYj4So=; b=aeNfzRe7NClIz+0PGF3JVQraiXruWifk8KHC5VrATxYcuSZacEjqCIgTwcufh+DeJB WGHN5o8j5rYfvM66tZzBzcyGzh7o7DI36TZn73SsbvnC1GpOTxOeT3qTegdMtgiz6GyQ D475ukrPrPp/PMXgT8luIZrtohUltK58VvUkvP+2O6pef9+3+EvgKMoFNgyXqMYmRkd9 VmbLPrAJZ/a0VFzEAVcmKcfOmz5r8ivtWh4WikmmHxYRn3Dl5xSUJUTiQ8VIKF45eJcm x2A87UC0NJS++M41/qaqhFfiwG5fKJ8mYohYY1w7/HYoOeXWlU9H6ov6njpjj1mJgTDa fKEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=g0qhrPaNFXprhc3cZYbGlbf//MPehpcRQRML1FYj4So=; b=aqi4p0tY9oanhBMLg1int252iGhn543Aosr8/GDAxmJF2hHBzYGe0XzYjWKixqsByD NJaVqend+ddfYjIWEIzHmEoPF+WBwNMUj0W/L8BIVqOEVEob7OtVDgxHgnY8Kwn0zy3T DKANQAp5IkKI5DzJkloTscjfkYuKhbH+Bp0wQqyUoVLYL3hxDKbwZsqhl60C5oyWT7ut wZb9xr9SeIRq6Wbuec7X0+XyH2DYEtAFv5Y0dOhyMTNNccCi93f9H6UB9zH+N2DlewVZ 9N3G0tvXsx3PdPx+csKpnFCfJtsHwzengl7mPPaTCot95WOGBWc5KCvrQnoGgC9klQVA Fc0Q== X-Gm-Message-State: AElRT7Gb5gZsGwO7t73wHQY+UM5KQ2qXb06LGH049s7PdbLgbMRxQMY8 x1qKKuag39wWffCB07MGQuxtmEWCAnizVbXVGVo= X-Received: by 10.107.159.76 with SMTP id i73mr902730ioe.0.1521187670007; Fri, 16 Mar 2018 01:07:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.34.71 with HTTP; Fri, 16 Mar 2018 01:07:49 -0700 (PDT) In-Reply-To: <20180315224727.GC73@LTA0271908.dhcp.ti.com> References: <20180316091355.2d2b7b04@canb.auug.org.au> <20180315224727.GC73@LTA0271908.dhcp.ti.com> From: Arnd Bergmann Date: Fri, 16 Mar 2018 09:07:49 +0100 X-Google-Sender-Auth: tAasubj62OnkV-YOppiB682kB1w Message-ID: Subject: Re: linux-next: build failure after merge of the asm-generic tree To: Bin Liu , Stephen Rothwell , Arnd Bergmann , Linux-Next Mailing List , Linux Kernel Mailing List , Greg Kroah-Hartman , Aaron Wu 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 On Thu, Mar 15, 2018 at 11:47 PM, Bin Liu wrote: > Hi, > > On Fri, Mar 16, 2018 at 09:13:55AM +1100, Stephen Rothwell wrote: >> Hi Arnd, >> >> After merging the asm-generic tree, today's linux-next build (arm >> multi_v7_defconfig) failed like this: >> >> drivers/usb/musb/musb_host.c: In function 'musb_rx_reinit': >> drivers/usb/musb/musb_host.c:577:10: error: 'struct musb' has no member named 'double_buffer_not_ok' >> if (musb->double_buffer_not_ok) >> ^~ >> drivers/usb/musb/musb_host.c: In function 'musb_ep_program': >> drivers/usb/musb/musb_host.c:807:12: error: 'struct musb' has no member named 'double_buffer_not_ok' >> if (musb->double_buffer_not_ok) { >> ^~ >> >> Caused by commit >> >> 8312c0cad792 ("usb: musb: remove blackfin port") Sorry about that, I should have done more testing after updating the patch. Aaron sent a second version of the blackfin removal, and after comparing his version with mine, I picked up a couple of extra hunks that I folded into my patch series, including the two musb bits below. > I don't have a clone of the asm-generic tree to check, but this patch > Arnd sent yesterday for review doesn't remove double_buffer_not_ok from > struct musb. Is it removed when Arnd you were revising it based on my > review comments? Anyway, it is better to remove it too since this flag > is Blackfin specific, but is it possible to combine this fixup patch with the > original patch to avoid bisect headache in the future? Sure, doing that now. Arnd 8<--- diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c index 011c8ca7de42..13486588e561 100644 --- a/drivers/usb/musb/musb_core.c +++ b/drivers/usb/musb/musb_core.c @@ -2166,7 +2166,7 @@ musb_init_controller(struct device *dev, int nIrq, void __iomem *ctrl) * - initializes musb->xceiv, usually by otg_get_phy() * - stops powering VBUS * - * There are various transceiver configurations. Blackfin, + * There are various transceiver configurations. * DaVinci, TUSB60x0, and others integrate them. OMAP3 uses * external/discrete ones in various flavors (twl4030 family, * isp1504, non-OTG, etc) mostly hooking up through ULPI. diff --git a/drivers/usb/musb/musb_core.h b/drivers/usb/musb/musb_core.h index ac675b1a34c4..8a74cb2907f8 100644 --- a/drivers/usb/musb/musb_core.h +++ b/drivers/usb/musb/musb_core.h @@ -414,19 +414,6 @@ struct musb { struct usb_gadget_driver *gadget_driver; /* its driver */ struct usb_hcd *hcd; /* the usb hcd */ - /* - * FIXME: Remove this flag. - * - * This is only added to allow Blackfin to work - * with current driver. For some unknown reason - * Blackfin doesn't work with double buffering - * and that's enabled by default. - * - * We added this flag to forcefully disable double - * buffering until we get it working. - */ - unsigned double_buffer_not_ok:1; - const struct musb_hdrc_config *config; int xceiv_old_state;