All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Mon, 3 Jan 2022 14:23:54 +0100	[thread overview]
Message-ID: <YdL46pTsM5dloS3n@kroah.com> (raw)
In-Reply-To: <f5351a32-18d1-9426-1060-42d658435247@ti.com>

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

  reply	other threads:[~2022-01-03 13:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 22:34 mux for 5.17-rc1 Peter Rosin
2022-01-02 22:38 ` [PATCH 1/6] dt-bindings: ti-serdes-mux: Add defines for J721S2 SoC Peter Rosin
2022-01-02 22:38 ` [PATCH 2/6] dt-bindings: mux: Document mux-states property Peter Rosin
2022-01-02 22:38 ` [PATCH 3/6] mux: Add support for reading mux state from consumer DT node Peter Rosin
2022-01-03 12:43   ` Greg Kroah-Hartman
2022-01-03 13:05     ` Aswath Govindraju
2022-01-03 13:23       ` Greg Kroah-Hartman [this message]
2022-01-02 22:38 ` [PATCH 4/6] mux: add missing mux_state_get Peter Rosin
2022-01-03 12:42   ` Greg Kroah-Hartman
2022-01-03 17:26     ` Peter Rosin
2022-01-06 14:41       ` Greg Kroah-Hartman
2022-01-07  7:10         ` Peter Rosin
2022-01-02 22:38 ` [PATCH 5/6] mux: fix grammar, missing "is" Peter Rosin
2022-01-03 12:37   ` Greg Kroah-Hartman
2022-01-02 22:38 ` [PATCH 6/6] mux: Fix struct mux_state kernel-doc comment Peter Rosin
2022-01-03 12:46 ` mux for 5.17-rc1 Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YdL46pTsM5dloS3n@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=a-govindraju@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.