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 X-Spam-Level: X-Spam-Status: No, score=-11.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 26079C4332D for ; Fri, 15 Jan 2021 18:21:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 04CC723AA9 for ; Fri, 15 Jan 2021 18:21:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388743AbhAOSVT (ORCPT ); Fri, 15 Jan 2021 13:21:19 -0500 Received: from mail.kernel.org ([198.145.29.99]:43862 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726434AbhAOSVR (ORCPT ); Fri, 15 Jan 2021 13:21:17 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 13EE923AA7; Fri, 15 Jan 2021 18:20:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1610734836; bh=yywxwDqzhCGsowbf6Lp1h6NAOX0mTHDYPddZyQTe1ZA=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=HVtOaB4YVRF7tyEqDy4FPLguR4hJxrNBUgjNdbrKtR51R6rZp0c9OY9pednANeGcZ 5eqpEZf6JRVve4q1AETTslDOCyOeqhJcO2QO1Tvd2GziUQ8yM8HWMz7iQT9a1OKMwV tsHBqxLf+RRRogOXIebyHFv3QdnUQ9xWC3Iuk09c2ekCbm80REl0Rjyf97b0lH2/WZ i1ZVPmjook3gxY+0c3LjT5bZVT+xkXDlQ0HPK7K6XaCGum6ySerJA0z2bzpvzzbg1x kj2zMV8Y9KNYOXWCuTZuPvmcFkeTndukZ76VcYBWfRiGGwUQhaTUH6PQ/OgEu39j3b dR/elNyIMXQug== From: Mark Brown To: Adrien Grassein Cc: robh+dt@kernel.org, linux-kernel@vger.kernel.org, jagan@amarulasolutions.com, devicetree@vger.kernel.org, lgirdwood@gmail.com In-Reply-To: <20210113222016.1915993-1-adrien.grassein@gmail.com> References: <20210113222016.1915993-1-adrien.grassein@gmail.com> Subject: Re: [PATCH v4 0/6] Fix issues on pf8x00 driver Message-Id: <161073479107.12431.7161364443941484976.b4-ty@kernel.org> Date: Fri, 15 Jan 2021 18:19:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Jan 2021 23:20:10 +0100, Adrien Grassein wrote: > this patch set aims is to fix some issues contains in the pf8x00 driver. > Some issues are documentation ones, some others are in code. > > These issues where found while developing another version of the same > driver. I prefer to share with you the patch for it. > > I do these patches on the master branch of the linux-next repository. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/6] regulator: pf8x00: add a doc for the module commit: 4d23b84d1fcd1eadbc5c6cd93e76b02a8d191d66 [2/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc commit: 988d0d42509a2c1fad0844a6e8f9c7bce7c930dd [3/6] regulator: dt-bindings: pf8x00: mark nxp,ilim-ma property as deprecated commit: 34b860aa0b6221b21eea6bac76357063f525b561 [4/6] regulator: pf8x00: mark nxp,ilim-ma property as deprecated commit: 245f5f65229a6c6f5b04fa90221b44818a928916 [5/6] regulator: pf8x00: use linear range for buck 1-6 commit: 35a93349932e0e04c284f8a4954f3d1236c97d85 [6/6] regulator: pf8x00: fix nxp,phase-shift commit: 475a5d85ff62f7ca73f51f23977e7e3ec8c9f906 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark