From: Dave Jones <davej@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk, Mike Galbraith <efault@gmx.de>
Subject: Re: p4_clockmod broken in 2.6.16-rc? kernels
Date: Fri, 10 Mar 2006 00:47:23 -0500 [thread overview]
Message-ID: <20060310054723.GC5600@redhat.com> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60077E8338@scsmsx403.amr.corp.intel.com>
On Thu, Mar 09, 2006 at 08:07:44PM -0800, Pallipadi, Venkatesh wrote:
>
> Great to hear that the patch helped. I had a typo in the patch header
> and attaching an updated patch.
>
> Dave: Please push this patch towards base. This was a bug in one of the
> recent changes in p4-clockmod.c
Applied, thanks. I fixed this one up by hand, but next time can you
inline the patch instead of attaching it ?
git doesn't grok MIME, so I end up having to save it seperately,
and munge it back into your mail in an editor before I can feed it to
git, turning 'a few seconds' into a 'a minute or two' to apply a patch.[1]
btw, should acpi-cpufreq/speedstep-ich also have those errata workarounds?
Thanks.
Dave
[1] Actually this was even longer. Due to me missing chopping a MIME
mailheader, it still confused git-apply, and I scratched my head
for some time until Linus clued me in. MIME- just say no!
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-10 5:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 4:07 p4_clockmod broken in 2.6.16-rc? kernels Pallipadi, Venkatesh
2006-03-10 5:47 ` Dave Jones [this message]
2006-03-14 17:55 ` Venkatesh Pallipadi
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 13:53 Pallipadi, Venkatesh
2006-03-10 3:25 ` Mike Galbraith
2006-03-09 6:11 Mike Galbraith
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=20060310054723.GC5600@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=efault@gmx.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 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.