cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq@lists.linux.org.uk, Goran <gkoruga@siol.net>
Subject: Re: cpufreq and modular build
Date: Sun, 11 May 2008 12:18:18 -0400	[thread overview]
Message-ID: <20080511161818.GG15445@codemonkey.org.uk> (raw)

On Tue, May 06, 2008 at 05:12:43PM +0200, Thomas Renninger wrote:
 >
 > On Mon, 2008-05-05 at 17:58 +0200, Goran wrote:
 > >           To compile this driver as a module, choose M here: the
 > >           module will be called cpufreq.
 >
 > This should just be cut out. Could you send a patch?

We fixed this back in November!
Commit 232e8884cb62f865d69383e42ef333215da504d4

        Dave

             reply	other threads:[~2008-05-11 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 16:18 Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-05 15:58 cpufreq and modular build Goran
2008-05-06 15:12 ` Thomas Renninger
2008-05-11 13:48   ` Goran

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=20080511161818.GG15445@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=gkoruga@siol.net \
    --cc=trenn@suse.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