From: Stephen Boyd <sboyd@kernel.org>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/7] drivers: clk: unexport clk_register_gpio_gate()
Date: Sun, 05 Jan 2020 12:12:48 -0800 [thread overview]
Message-ID: <20200105201249.572A22077B@mail.kernel.org> (raw)
In-Reply-To: <20191128144450.24094-1-info@metux.net>
Quoting Enrico Weigelt, metux IT consult (2019-11-28 06:44:44)
> The function clk_register_gpio_gate() doesn't seem to have any users
> outside clk-gpio.c, thus unexport and make it static.
>
> Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
> ---
Is any of this patch series relevant when [1] is applied? I think I will
just apply that patch instead.
[1] https://lkml.kernel.org/r/20190830150923.259497-2-sboyd@kernel.org
prev parent reply other threads:[~2020-01-05 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 14:44 [PATCH 1/7] drivers: clk: unexport clk_register_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 2/7] drivers: clk: unexport clk_hw_register_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 3/7] include: linux: clk-provider: remove obsolete clk_hw_unregister_gpio_gate() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 4/7] drivers: clk: unexport clk_register_gpio_mux() Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 5/7] drivers: clk: unexport clk_gpio_mux_ops field Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 6/7] drivers: clk: unexport clk_gpio_gate_ops field Enrico Weigelt, metux IT consult
2019-11-28 14:44 ` [PATCH 7/7] drivers: clk: unexport clk_hw_register_gpio_mux() Enrico Weigelt, metux IT consult
2020-01-05 20:12 ` Stephen Boyd [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=20200105201249.572A22077B@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=info@metux.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
/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.