From: Thomas Gleixner <tglx@linutronix.de>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Mark Rutland <mark.rutland@arm.com>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel
Date: Sat, 15 Nov 2014 02:09:29 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1411150154280.3909@nanos> (raw)
In-Reply-To: <CAOMFOmV5=tes6Ak1eUKb2qircp8ba6jt6v-bg66Kp_-jYk9m2w@mail.gmail.com>
On Fri, 14 Nov 2014, Anatol Pomozov wrote:
> On Fri, Nov 14, 2014 at 4:18 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >> So what I suppose to do with my patch? If it does not work could
> >> anyone provide patch that removes ARM arch dependency from
> >> tegra20_timer.c?
> >
> > Huch? You want other people to solve your problems?
>
> This is not the point. I provided patch that fixes the issue. Other
> people said that they have ideas how to do it different (and better)
> way. So I am asking to share these ideas represented as a patch.
That's not the way it works.
You sent a patch to solve an problem which you are facing.
Now the people who review the patch think that there is a better
approach than moving code from arm/ to the timekeeping core code.
So it's up to you to come up with a patch which solves the problem in
the right way.
Thanks,
tglx
next prev parent reply other threads:[~2014-11-15 1:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:34 Anatol Pomozov
2014-11-07 19:42 ` Anatol Pomozov
2014-11-10 9:53 ` Thierry Reding
2014-11-10 19:26 ` Anatol Pomozov
2014-11-13 22:46 ` Thomas Gleixner
2014-11-13 23:21 ` John Stultz
2014-11-14 0:26 ` Thomas Gleixner
2015-01-09 9:43 ` Thierry Reding
2015-01-09 19:18 ` John Stultz
2014-11-14 22:03 ` Anatol Pomozov
2014-11-15 0:18 ` Thomas Gleixner
2014-11-15 0:51 ` Anatol Pomozov
2014-11-15 1:09 ` Thomas Gleixner [this message]
2014-11-15 1:38 ` Thomas Gleixner
2015-01-09 9:49 ` Thierry Reding
2015-01-09 13:59 ` Mark Rutland
2015-01-09 14:09 ` Thierry Reding
2015-01-09 19:48 ` Paul Walmsley
2015-01-09 13:30 ` Daniel Lezcano
2014-11-15 1:07 ` Stephen Warren
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=alpine.DEB.2.11.1411150154280.3909@nanos \
--to=tglx@linutronix.de \
--cc=anatol.pomozov@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®