From: "Måns Rullgård" <mans@mansr.com>
To: Mason <slash.tmp@free.fr>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: Trivial clocksource driver
Date: Tue, 29 Sep 2015 21:18:10 +0100 [thread overview]
Message-ID: <yw1xwpv9ou7x.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <560AEB32.50006@free.fr> (Mason's message of "Tue, 29 Sep 2015 21:49:06 +0200")
Mason <slash.tmp@free.fr> writes:
> On 29/09/2015 20:32, Thomas Gleixner wrote:
>
>> On Tue, 29 Sep 2015, Mason wrote:
>>
>>> I am trying to submit a new ARM port, and Arnd pointed out that the
>>> clocksource code could not live in arch/arm/$PLATFORM, but had to
>>> move to drivers/clocksource (and it had to support DT).
>>>
>>> Did I understand correctly? Is this the right place to submit code
>>> as provided below?
>>
>> Yes, drivers/clocksource is the right place. You just need to submit a
>> formal patch, which includes a proper subject line, changelog, plus
>> the necessary Makefile and Kconfig modifications.
>
> OK, I'll send a formal patch tomorrow.
> There are no Kconfig modifications, is that OK?
Why don't you use my driver? It's even simpler, and it works just fine
on the 87xx chip.
https://github.com/mansr/linux-tangox/blob/master/drivers/clocksource/clksrc-tangox.c
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2015-09-29 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:25 Mason
2015-09-29 18:32 ` Thomas Gleixner
2015-09-29 19:49 ` Mason
2015-09-29 20:18 ` Måns Rullgård [this message]
2015-09-29 20:49 ` Thomas Gleixner
2015-09-29 21:12 ` Mason
2015-09-29 21:55 ` Måns Rullgård
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=yw1xwpv9ou7x.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slash.tmp@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome