From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>,
"Thomas Gleixner" <tglx@linutronix.de>, "Andi Kleen" <ak@suse.de>,
"Ingo Molnar" <mingo@elte.hu>,
"Chris Wright" <chrisw@sous-sol.org>
Subject: Re: [PATCH 1/8] Restructuring hpet timer generic clock interfaces
Date: Wed, 9 May 2007 00:28:34 +0300 [thread overview]
Message-ID: <200705090028.34969.caglar@pardus.org.tr> (raw)
In-Reply-To: <653FFBB4508B9042B5D43DC9E18836F55DF62B@scsmsx415.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
09 May 2007 Çar tarihinde, Pallipadi, Venkatesh şunları yazmıştı:
> That's good news :-).
>
> Can you send me the full dmesg with the 5 patches and also the config file
> you are using. Also, did you try these patches against 2.6.21-vanilla or
> recent git?
I'm trying these on top of 2.6.21.1 + CFS-v11 and with some other patches
(bootsplash + apparmor + swap prefetch + your ondemand timer patch)
You can find config.gz and full dmesg at [1]
[1] http://cekirdek.pardus.org.tr/~caglar/hpet/
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-08 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 20:27 [PATCH 1/8] Restructuring hpet timer generic clock interfaces Venki Pallipadi
2007-05-07 23:47 ` S.Çağlar Onur
2007-05-08 2:40 ` Pallipadi, Venkatesh
2007-05-08 21:07 ` S.Çağlar Onur
2007-05-08 21:22 ` Pallipadi, Venkatesh
2007-05-08 21:28 ` S.Çağlar Onur [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=200705090028.34969.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.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