From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Rosin <peda@axentia.se>
Cc: Aswath Govindraju <a-govindraju@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] mux-for-5.17-rc1
Date: Fri, 4 Feb 2022 15:47:41 +0100 [thread overview]
Message-ID: <Yf08jcyZfESaYlVr@kroah.com> (raw)
In-Reply-To: <bd26e410-b2c4-888c-9bef-efc26146e366@axentia.se>
On Fri, Jan 07, 2022 at 08:43:43AM +0100, Peter Rosin wrote:
> Hi Greg!
>
> Since last I improved a couple of commit messages. I.e. adding a body to
> "mux: fix grammar, missing "is"."
> and a Link tag to
> "mux: Add support for reading mux state from consumer DT node"
>
> Further, I removed the exports of the new functions mux_state_get()
> and mux_state_put() as there are no users, not even in the wings as
> is the case for devm_mux_state_get().
>
> Cheers,
> Peter
>
> Aswath Govindraju (1):
> mux: Add support for reading mux state from consumer DT node
>
> Peter Rosin (2):
> mux: add missing mux_state_get
> mux: fix grammar, missing "is".
>
> Yang Li (1):
> mux: Fix struct mux_state kernel-doc comment
>
> .../driver-api/driver-model/devres.rst | 1 +
> drivers/mux/core.c | 239 ++++++++++++++++--
> include/linux/mux/consumer.h | 18 ++
> 3 files changed, 236 insertions(+), 22 deletions(-)
>
Sorry for the delay, now applied.
greg k-h
prev parent reply other threads:[~2022-02-04 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 7:43 Peter Rosin
2022-01-07 7:44 ` [PATCH v2 1/4] mux: Add support for reading mux state from consumer DT node Peter Rosin
2022-01-07 7:44 ` [PATCH v2 2/4] mux: add missing mux_state_get Peter Rosin
2022-01-07 7:44 ` [PATCH v2 3/4] mux: fix grammar, missing "is" Peter Rosin
2022-01-07 7:44 ` [PATCH v2 4/4] mux: Fix struct mux_state kernel-doc comment Peter Rosin
2022-02-04 14:47 ` Greg Kroah-Hartman [this message]
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=Yf08jcyZfESaYlVr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome