From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
Chris Healy <cphealy@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] clk: Sync prototypes for clk_bulk_enable()
Date: Wed, 17 Jul 2019 07:53:26 -0700 [thread overview]
Message-ID: <CAHQ1cqHCbObjpD4p-WVQmoP3Jth=j3ap-qCjuETj416rCBtjLg@mail.gmail.com> (raw)
In-Reply-To: <20190715220043.55E8A20665@mail.kernel.org>
On Mon, Jul 15, 2019 at 3:00 PM Stephen Boyd <sboyd@kernel.org> wrote:
>
> Quoting Andrey Smirnov (2019-07-15 13:12:29)
> > No-op version of clk_bulk_enable() should have the same protoype as
> > the real implementation, so constify the last argument to make it so.
> >
> > Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> > Cc: Russell King <linux@armlinux.org.uk>
> > Cc: Chris Healy <cphealy@gmail.com>
> > Cc: linux-clk@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > ---
>
> No cover letter, but I'm inclined to squash these all together into one
> patch instead of 6. I'm not sure why each function gets a different
> patch.
>
Sure, will squash all in v2.
Thanks,
Andrey Smirnov
prev parent reply other threads:[~2019-07-17 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 20:12 [PATCH 1/6] clk: Sync prototypes for clk_bulk_enable() Andrey Smirnov
2019-07-15 20:12 ` [PATCH 2/6] clk: Sync prototypes for clk_bulk_prepare() Andrey Smirnov
2019-07-15 20:12 ` [PATCH 3/6] clk: Constify second argument of clk_bulk_prepare_enable() Andrey Smirnov
2019-07-15 20:12 ` [PATCH 4/6] clk: Sync prototypes for clk_bulk_disable() Andrey Smirnov
2019-07-15 20:12 ` [PATCH 5/6] clk: Sync prototypes for clk_bulk_unprepare() Andrey Smirnov
2019-07-15 20:12 ` [PATCH 6/6] clk: Constify second argument of clk_bulk_disable_unprepare() Andrey Smirnov
2019-07-15 22:00 ` [PATCH 1/6] clk: Sync prototypes for clk_bulk_enable() Stephen Boyd
2019-07-17 14:53 ` Andrey Smirnov [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='CAHQ1cqHCbObjpD4p-WVQmoP3Jth=j3ap-qCjuETj416rCBtjLg@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sboyd@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).