From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Sean Young <sean@mess.org>
Cc: cpufreq@zenii.linux.org.uk
Subject: Re: [PATCH] AMD Elan SC520 cpufreq driver
Date: Tue, 29 Mar 2005 23:50:29 +0200 [thread overview]
Message-ID: <4249CDA5.8060208@tremplin-utc.net> (raw)
In-Reply-To: <20050329213658.GA12868@levin.pad.mess.org>
Sean Young a écrit :
> Here is a cpufreq driver for the AMD Elan SC520, diff against
> 2.6.12-rc1.
[snipped]
> + * 2005-03-30: - initial revision
^^^^^^^^^^
Well, not that I'm really concerned, but just by curiosity, I've seen
this patch in the cpu-freq snapshot since 2005-03-23, how does it happen
that you submit it only now, and with a release date of tomorrow?
Timewrapping?
Eric
next prev parent reply other threads:[~2005-03-29 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 21:36 [PATCH] AMD Elan SC520 cpufreq driver Sean Young
2005-03-29 21:50 ` Eric Piel [this message]
2005-03-29 23:42 ` Sean Young
2005-03-29 22:04 ` Dominik Brodowski
2005-04-03 16:27 ` Sean Young
2005-04-03 23:53 ` Eric Piel
2005-04-09 20:20 ` [PATCH] cpufreq: fix latency comment in cpufreq.h [Was: Re: [PATCH] AMD Elan SC520 cpufreq driver] Dominik Brodowski
2005-04-09 21:43 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2005-05-29 1:43 [PATCH] AMD Elan SC520 cpufreq driver Sean Young
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=4249CDA5.8060208@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=cpufreq@zenii.linux.org.uk \
--cc=sean@mess.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