From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1FA09CFB451 for ; Mon, 7 Oct 2024 18:13:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=No0Hx8JTeZm9V48Hw6YQWLvbytv7zg1cNl8vDMdRiuI=; b=lbi6psDB4xf4Xh B62jfPT1BGXdlK8+oZKOuBfZqJAaL7gXnrpOf5H6tcEkMS4hMGKu0clbtM3aKXyHRghOESaZV6z7J 27T011Q1AK0VqEFVQ7+qAQ5LT6k/NHeNIlHTUC11nlV/9MO2EjwwUrmAbkvnPSKCZbAZI1kktoU66 riyTk0HOlp2bu9kkIzqRxYaFwLP7a5BiTAzklbyJAeSeerHUNpTOJJ0AR+6DLGpcilC5xtGO2VbNi X+UFWJnyfnoZK+6fguxLe05Og18l0d98LQ0nEQb+ITDPEUM0Dnk0JxZ+w13nqwjiTRq4ggdgHD2Xb S8lpcQ6HjcTqdZ6hwF3w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1sxsEc-00000003RIY-3W87; Mon, 07 Oct 2024 18:13:30 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1sxsDc-00000003R6o-41Rh for linux-phy@lists.infradead.org; Mon, 07 Oct 2024 18:12:30 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id E12255C5D32; Mon, 7 Oct 2024 18:12:23 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5AA43C4CEC7; Mon, 7 Oct 2024 18:12:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1728324747; bh=MVMcREqOQie9bCu+l3+EHtHOGyR8Vt6zdS95oQnMRi8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gonMD3Z81MR5tRjnQ0yJmdqAu47JdQCbp7tEX2A21sXKlMP/BEUVUIIhtq8FtSqMx v+rzR4G4ssygEQJ9YqcBXdmQOw6weTueOk+MWD+Sv6TQVohLCiBbGQ6wntvJad2ghQ /mdKHhu1pRsMOMJk4rYFOdvZpMMUsIQezchlhaDPPYk2X+SBaD0s9ZbdHFHTtXzX2R l1cLTPzVPlKpjantP9FGyeD77s1gxCHRdcDCTlHjS1MAUjJQqHbxWAyc2A6AatXFbt Knh3eQXEiZJVxeOIMEkTdvsHZaxeq8xY+QGQGthQ9oqfHv0RGjhJhxiTuOwDYepBR3 p/XtFo3K7Xh1w== Date: Mon, 7 Oct 2024 23:42:23 +0530 From: Vinod Koul To: Florian Fainelli Cc: Justin Chen , Al Cooper , Sam Edwards , Broadcom internal kernel review list , Kishon Vijay Abraham I , linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org Subject: Re: (subset) [PATCH v2 0/2] phy: usb: Broadcom BCM4908 USB init fixes Message-ID: References: <20241004034131.1363813-1-CFSworks@gmail.com> <172831613316.134526.5485203085922304367.b4-ty@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241007_111229_083741_87384958 X-CRM114-Status: GOOD ( 14.01 ) X-BeenThere: linux-phy@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux Phy Mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-phy" Errors-To: linux-phy-bounces+linux-phy=archiver.kernel.org@lists.infradead.org On 07-10-24, 10:06, Florian Fainelli wrote: > On 10/7/24 08:48, Vinod Koul wrote: > > > > On Thu, 03 Oct 2024 20:41:29 -0700, Sam Edwards wrote: > > > This is v2 of my previous patch [1] targeted at resolving a crash-on-boot on > > > the BCM4908 family due to a missized table. > > > > > > Changes v1->v2: > > > - Florian requested this change be broken into an immediate bugfix (w/ the > > > 'fixes' tag) and a second patch containing the coding change aimed at > > > preventing this problem from happening again > > > > > > [...] > > > > Applied, thanks! > > > > [2/2] phy: usb: update Broadcom driver table to use designated initializers > > commit: d3712b35f3c694cb932f87194caafc714109ea08 > > I looked at your tree and both patches are applied in the "next" branch and > the first one is also in the "fixes" branch, thanks Vinod! First one should go into fixes, whereas second on next (due to dependency merged fixes into next) -- ~Vinod -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6DADE1D95AA for ; Mon, 7 Oct 2024 18:12:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728324748; cv=none; b=K4UacvmN8zoT+jjI96LTvdgAdVEKFVfiGvWabzgDB0Vn69cDu1osjjQZ6xLWRYOjkQ+Lh1Z1x/hCcVI7rDmiZFEigr0TIn+bd3Ppq1JNM/9OkLyRC/xWgH4oMl9gAoikNp2sbDfHeH1YpETg/odiP6gGG7lk6QeKcP9P+sEI7lw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728324748; c=relaxed/simple; bh=MVMcREqOQie9bCu+l3+EHtHOGyR8Vt6zdS95oQnMRi8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lH9zK48s1fX9ennlLL4jsEABpoczD/bezeSlZFQMDxJpz8IPwqZaEHQPDY0A6W/n7aR6mBnGTq3i/Pa4MuDQ5y6CGEHlV7COfuAHWnwb1UGXPbwg9J4ENAmXG0Sgem8H3n4PqIMqAnGuLXSi5awkqm+EaUA/EE9i13MWNsGf8vI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gonMD3Z8; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gonMD3Z8" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5AA43C4CEC7; Mon, 7 Oct 2024 18:12:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1728324747; bh=MVMcREqOQie9bCu+l3+EHtHOGyR8Vt6zdS95oQnMRi8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gonMD3Z81MR5tRjnQ0yJmdqAu47JdQCbp7tEX2A21sXKlMP/BEUVUIIhtq8FtSqMx v+rzR4G4ssygEQJ9YqcBXdmQOw6weTueOk+MWD+Sv6TQVohLCiBbGQ6wntvJad2ghQ /mdKHhu1pRsMOMJk4rYFOdvZpMMUsIQezchlhaDPPYk2X+SBaD0s9ZbdHFHTtXzX2R l1cLTPzVPlKpjantP9FGyeD77s1gxCHRdcDCTlHjS1MAUjJQqHbxWAyc2A6AatXFbt Knh3eQXEiZJVxeOIMEkTdvsHZaxeq8xY+QGQGthQ9oqfHv0RGjhJhxiTuOwDYepBR3 p/XtFo3K7Xh1w== Date: Mon, 7 Oct 2024 23:42:23 +0530 From: Vinod Koul To: Florian Fainelli Cc: Justin Chen , Al Cooper , Sam Edwards , Broadcom internal kernel review list , Kishon Vijay Abraham I , linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org Subject: Re: (subset) [PATCH v2 0/2] phy: usb: Broadcom BCM4908 USB init fixes Message-ID: References: <20241004034131.1363813-1-CFSworks@gmail.com> <172831613316.134526.5485203085922304367.b4-ty@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 07-10-24, 10:06, Florian Fainelli wrote: > On 10/7/24 08:48, Vinod Koul wrote: > > > > On Thu, 03 Oct 2024 20:41:29 -0700, Sam Edwards wrote: > > > This is v2 of my previous patch [1] targeted at resolving a crash-on-boot on > > > the BCM4908 family due to a missized table. > > > > > > Changes v1->v2: > > > - Florian requested this change be broken into an immediate bugfix (w/ the > > > 'fixes' tag) and a second patch containing the coding change aimed at > > > preventing this problem from happening again > > > > > > [...] > > > > Applied, thanks! > > > > [2/2] phy: usb: update Broadcom driver table to use designated initializers > > commit: d3712b35f3c694cb932f87194caafc714109ea08 > > I looked at your tree and both patches are applied in the "next" branch and > the first one is also in the "fixes" branch, thanks Vinod! First one should go into fixes, whereas second on next (due to dependency merged fixes into next) -- ~Vinod