From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
hpa@zytor.com, mingo@kernel.org, paul.gortmaker@windriver.com,
Linus Walleij <linus.walleij@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: linux-tip-commits@vger.kernel.org, Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [tip:timers/core] clocksource: Increase dependencies of timer-stm32 to limit build wreckage
Date: Mon, 29 Jun 2015 11:09:18 +0200 [thread overview]
Message-ID: <55910B3E.9070405@linaro.org> (raw)
In-Reply-To: <CALszF6BXpgW109mTW_nF0yexdKkptwFQXHkzBnZ9MZN520PVYA@mail.gmail.com>
On 06/22/2015 10:05 AM, Maxime Coquelin wrote:
[ ... ]
>> ---
>> drivers/clocksource/Kconfig | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>
> Thanks Paul for the patch.
> Actually, I already had sent a patch to fix this dependency issue [0].
> I thought Daniel had pick it, but don't find it in his tree.
> My patch adds a build dependency on GENERIC_CLOCKEVENTS, which I think
> is the best way to fix the problem.
Yes, I have it in my tree but I was expecting some more fixes to pick up
in order to send a PR to Thomas.
Is it possible you send your a fix on top of this patch ? So I can drop
your initial patch.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-06-29 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 23:02 [PATCH] clocksource: increase dependencies of timer-stm32 to limit build wreckage Paul Gortmaker
2015-06-20 23:02 ` Paul Gortmaker
2015-06-21 18:03 ` [tip:timers/core] clocksource: Increase " tip-bot for Paul Gortmaker
2015-06-22 8:05 ` Maxime Coquelin
2015-06-29 9:09 ` Daniel Lezcano [this message]
2015-06-30 7:46 ` Maxime Coquelin
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=55910B3E.9070405@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=hpa@zytor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
/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.