From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Timer code duplication in driver
Date: Tue, 16 Aug 2005 16:42:37 +0000 [thread overview]
Message-ID: <20050816164237.GA4144@us.ibm.com> (raw)
In-Reply-To: <4301E1D7.5070707@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On 16.08.2005 [14:53:43 +0200], Oliver Korpilla wrote:
> Hello!
>
> I was just reviewing code about high resolution timers for learning to
> use their API correctly, and have come to the following code duplication
> (in 2.6.12.4 kernel.org):
<snip>
> Anyone else thinking this should be fixed?
>
> Could someone please review this?
Your best bet is to write a patch and send it to Corey Minyard, George
Anzinger and the high-res-timers list, cc-ing KJ again... I think you
are right, but it's Corey's code and George's subsystem.
Thanks,
Nish
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-08-16 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 12:53 [KJ] Timer code duplication in driver Oliver Korpilla
2005-08-16 16:42 ` Nishanth Aravamudan [this message]
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=20050816164237.GA4144@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@vger.kernel.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 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.