From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
Mikael Pettersson <mikpe@it.uu.se>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic v2
Date: Tue, 3 Nov 2009 14:51:41 +0100 [thread overview]
Message-ID: <63386a3d0911030551j1accd6fby7038895df544385b@mail.gmail.com> (raw)
In-Reply-To: <63386a3d0910251518i42149642g183f2d3f6c43384f@mail.gmail.com>
2009/10/25 Linus Walleij <linus.ml.walleij@gmail.com>:
> 2009/10/21 Linus Walleij <linus.walleij@stericsson.com>:
>
>> Changes v1->v2:
>> - Fixed Mikaels comments: spelling, terminology.
>> - Kept the functions inline: all uses and foreseen uses
>> are once per kernel and all are in __init or __cpuinit sections.
>> - Unable to break out common code - the code is not common and
>> implementing two execution paths will be more awkward.
>> - Hoping the tglx likes it anyway.
>
> Ping on tglx on this, I will uninline the functions if you think
> it's better in the long run, just tell me, else can you pick this
> patch?
Ping again...
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org,
Mikael Pettersson <mikpe@it.uu.se>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic v2
Date: Tue, 3 Nov 2009 14:51:41 +0100 [thread overview]
Message-ID: <63386a3d0911030551j1accd6fby7038895df544385b@mail.gmail.com> (raw)
Message-ID: <20091103135141.GKLubJjhrWbxK2QmMlu94iwoFy0MYBUSjBMt_HNFnV0@z> (raw)
In-Reply-To: <63386a3d0910251518i42149642g183f2d3f6c43384f@mail.gmail.com>
2009/10/25 Linus Walleij <linus.ml.walleij@gmail.com>:
> 2009/10/21 Linus Walleij <linus.walleij@stericsson.com>:
>
>> Changes v1->v2:
>> - Fixed Mikaels comments: spelling, terminology.
>> - Kept the functions inline: all uses and foreseen uses
>> are once per kernel and all are in __init or __cpuinit sections.
>> - Unable to break out common code - the code is not common and
>> implementing two execution paths will be more awkward.
>> - Hoping the tglx likes it anyway.
>
> Ping on tglx on this, I will uninline the functions if you think
> it's better in the long run, just tell me, else can you pick this
> patch?
Ping again...
Linus Walleij
next prev parent reply other threads:[~2009-11-03 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 22:33 [PATCH] Make MIPS dynamic clocksource/clockevent clock code generic v2 Linus Walleij
2009-10-20 22:33 ` Linus Walleij
2009-10-20 23:02 ` Mikael Pettersson
2009-10-25 22:18 ` Linus Walleij
2009-10-25 22:18 ` Linus Walleij
2009-11-03 13:51 ` Linus Walleij [this message]
2009-11-03 13:51 ` Linus Walleij
2009-11-03 15:29 ` Thomas Gleixner
2009-11-10 17:03 ` Thomas Gleixner
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=63386a3d0911030551j1accd6fby7038895df544385b@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mikpe@it.uu.se \
--cc=ralf@linux-mips.org \
--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