From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Manuel Lauss <manuel.lauss@gmail.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH v2 2/3] MIPS: Alchemy: preset loops_per_jiffy based on CPU clock
Date: Thu, 29 Jan 2015 19:33:29 +0300 [thread overview]
Message-ID: <54CA60D9.8080008@cogentembedded.com> (raw)
In-Reply-To: <1422544004-25254-2-git-send-email-manuel.lauss@gmail.com>
Hello.
On 01/29/2015 06:06 PM, Manuel Lauss wrote:
> This was lost during the rewrite of clock framework support.
> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> ---
> v2: more syntactic sugar for Sergei,
Thank you. At least I don't need syntactic insulin in order to digest it.
There's a risk of the semicolon cancer though. :-)
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-01-29 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:06 [PATCH v2 1/3] MIPS: Alchemy: fix Au1000/Au1500 LRCLK calculation Manuel Lauss
2015-01-29 15:06 ` [PATCH v2 2/3] MIPS: Alchemy: preset loops_per_jiffy based on CPU clock Manuel Lauss
2015-01-29 16:33 ` Sergei Shtylyov [this message]
2015-01-29 15:06 ` [PATCH v2 3/3] MIPS: Alchemy: remove declaration for set_cpuspec Manuel Lauss
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=54CA60D9.8080008@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.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