From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: export __clk_get_hw for re-use in others
Date: Wed, 22 Jan 2014 09:59:31 -0800 [thread overview]
Message-ID: <52E00703.5080001@codeaurora.org> (raw)
In-Reply-To: <CAEjAshrxXLJ-zFsTO9TnewYBBEPzFR1cixbLnD6U-U1EKdByxg@mail.gmail.com>
On 01/21/14 21:23, SeongJae Park wrote:
> On Wed, Jan 22, 2014 at 1:59 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> On Wed, Jan 22, 2014 at 12:05:57PM +0900, SeongJae Park wrote:
>>> Dear Greg, Mike,
>>>
>>> May I ask your answer or other opinion, please?
>> It's the middle of the merge window, it's not time for new development,
>> or much time for free-time for me, sorry. Feel free to fix it the best
>> way you know how.
> Oops, I've forgot about the merge window. Thank you very much for your
> kind answer.
> Sorry if I bothered you while you're in busy time.
> Because the build problem is not a big deal because it exists only in
> -next tree,
> I will wait until merge window be closed and then fix it again if it
> still exist.
>
I've already sent a patch that exports this and other clock provider
functions. Please use this one:
https://patchwork.kernel.org/patch/3507921/
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: SeongJae Park <sj38.park@gmail.com>,
Mike Turquette <mturquette@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: export __clk_get_hw for re-use in others
Date: Wed, 22 Jan 2014 09:59:31 -0800 [thread overview]
Message-ID: <52E00703.5080001@codeaurora.org> (raw)
In-Reply-To: <CAEjAshrxXLJ-zFsTO9TnewYBBEPzFR1cixbLnD6U-U1EKdByxg@mail.gmail.com>
On 01/21/14 21:23, SeongJae Park wrote:
> On Wed, Jan 22, 2014 at 1:59 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> On Wed, Jan 22, 2014 at 12:05:57PM +0900, SeongJae Park wrote:
>>> Dear Greg, Mike,
>>>
>>> May I ask your answer or other opinion, please?
>> It's the middle of the merge window, it's not time for new development,
>> or much time for free-time for me, sorry. Feel free to fix it the best
>> way you know how.
> Oops, I've forgot about the merge window. Thank you very much for your
> kind answer.
> Sorry if I bothered you while you're in busy time.
> Because the build problem is not a big deal because it exists only in
> -next tree,
> I will wait until merge window be closed and then fix it again if it
> still exist.
>
I've already sent a patch that exports this and other clock provider
functions. Please use this one:
https://patchwork.kernel.org/patch/3507921/
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-22 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 5:55 [PATCH] clk: export __clk_get_hw for re-use in others SeongJae Park
2014-01-19 5:55 ` SeongJae Park
2014-01-19 17:37 ` Greg KH
2014-01-19 17:37 ` Greg KH
2014-01-20 7:47 ` Mike Turquette
2014-01-20 7:47 ` Mike Turquette
2014-01-20 8:07 ` SeongJae Park
2014-01-20 8:07 ` SeongJae Park
2014-01-22 3:05 ` SeongJae Park
2014-01-22 3:05 ` SeongJae Park
2014-01-22 4:59 ` Greg KH
2014-01-22 4:59 ` Greg KH
2014-01-22 5:23 ` SeongJae Park
2014-01-22 5:23 ` SeongJae Park
2014-01-22 17:59 ` Stephen Boyd [this message]
2014-01-22 17:59 ` Stephen Boyd
2014-01-22 18:11 ` Mike Turquette
2014-01-22 18:11 ` Mike Turquette
2014-01-23 2:05 ` SeongJae Park
2014-01-23 2:05 ` SeongJae Park
2014-01-29 7:29 ` David Rientjes
2014-01-29 7:29 ` David Rientjes
2014-01-29 8:13 ` SeongJae Park
2014-01-29 8:13 ` SeongJae Park
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=52E00703.5080001@codeaurora.org \
--to=sboyd@codeaurora.org \
--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 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.