From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 1/4] clk: clk-s2mps11: Refactor for including support for other MFD clocks
Date: Wed, 29 Jan 2014 11:29:04 +0100 [thread overview]
Message-ID: <1390991344.2207.8.camel@AMDC1943> (raw)
In-Reply-To: <mvd17-4vW-3@gated-at.bofh.it>
Hi,
>
> Quoting Mark Brown (2013-12-31 08:09:16)
> > On Mon, Dec 30, 2013 at 09:33:50AM +0530, Tushar Behera wrote:
> >
> > > Commit 1b1ccee1e821 "mfd: s2mps11: Fix build after regmap field rename
> > > in sec-core.c" is also touching this file, which is in Mark's tree
> > > right now. If I rebase
> >
> > It's been in Linus' tree for a while now.
>
> OK, so I merged the two patches into clk-next, then merged clk-next into
> next-20131224 and the merge is super trivial to resolve. So I propose
> that we just let it get resolved in linux-next the usual way.
>
> Any objections? If not I'll take these two patches into clk-next.
Did you merged these patches into clk-next? Unfortunately I couldn't
find them (clk-next, next).
I am asking because I want to send patches with support for S2MPS14
clock (based on these patches).
Best regards,
Krzysztof
next parent reply other threads:[~2014-01-29 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m8Uox-5kN-11@gated-at.bofh.it>
[not found] ` <mtgmt-44E-3@gated-at.bofh.it>
[not found] ` <mtgmu-44E-27@gated-at.bofh.it>
[not found] ` <muwSe-WJ-17@gated-at.bofh.it>
[not found] ` <muCkW-RP-15@gated-at.bofh.it>
[not found] ` <mva3f-bR-7@gated-at.bofh.it>
[not found] ` <mvd17-4vW-3@gated-at.bofh.it>
2014-01-29 10:29 ` Krzysztof Kozlowski [this message]
2013-10-31 6:48 [PATCH 0/4] Add support for clocks in S5M8767 Tushar Behera
2013-12-26 10:18 ` [PATCH RESEND " Tushar Behera
2013-12-26 10:18 ` [PATCH RESEND 1/4] clk: clk-s2mps11: Refactor for including support for other MFD clocks Tushar Behera
2013-12-29 22:17 ` Mike Turquette
2013-12-30 4:03 ` Tushar Behera
2013-12-31 16:09 ` Mark Brown
2013-12-31 19:13 ` Mike Turquette
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=1390991344.2207.8.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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