Date:   Mon, 3 Jan 2022 14:23:54 +0100
From:   Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To:     Aswath Govindraju <a-govindraju@ti.com>
Cc:     Peter Rosin <peda@axentia.se>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] mux: Add support for reading mux state from consumer
 DT node
Message-ID: <YdL46pTsM5dloS3n@kroah.com>
References: <94ab71e1-2e68-def2-95b8-33162172f65c@axentia.se>
 <b9bb0b36-cf58-b436-6b72-c4211022981c@axentia.se>
 <YdLvX8TWBavEq8PH@kroah.com>
 <f5351a32-18d1-9426-1060-42d658435247@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f5351a32-18d1-9426-1060-42d658435247@ti.com>
Precedence: bulk

On Mon, Jan 03, 2022 at 06:35:52PM +0530, Aswath Govindraju wrote:
> Hi Greg,
> 
> On 03/01/22 6:13 pm, Greg Kroah-Hartman wrote:
> > On Sun, Jan 02, 2022 at 11:38:29PM +0100, Peter Rosin wrote:
> >> From: Aswath Govindraju <a-govindraju@ti.com>
> >>
> >> In some cases, we might need to provide the state of the mux to be set for
> >> the operation of a given peripheral. Therefore, pass this information using
> >> mux-states property.
> > 
> > Where is the user of this new function?
> > 
> 
> This function will be used by the following patch series,
> 
> https://lore.kernel.org/lkml/20211216041012.16892-1-a-govindraju@ti.com/t/
> 
> Since the above has a dependency on this patch series, it is planned to
> be merged after this series.

Please provide the users of new functions as part of the same series,
otherwise it is impossible to determine how the functions are used, or
if they are even used at all.

We try to not add functions with no in-tree users.

thanks,

greg k-h