cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 6426] Working Longhaul driver removed from kernel
Date: Mon, 10 Jul 2006 12:28:36 -0700	[thread overview]
Message-ID: <200607101928.k6AJSaHo031519@fire-2.osdl.org> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=6426

rafalbilski@interia.pl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|DEFERRED                    |CLOSED



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2006-07-10 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 19:28 bugme-daemon [this message]
     [not found] <bug-6426-3570@http.bugzilla.kernel.org/>
2008-03-12  1:18 ` [Bug 6426] Working Longhaul driver removed from kernel bugme-daemon
  -- strict thread matches above, loose matches on Subject: below --
2006-05-17 14:07 bugme-daemon
2006-04-30 19:40 bugme-daemon
2006-04-22 20:42 Rafał Bilski
2006-04-22 17:50 bugme-daemon
2006-04-22 17:42 bugme-daemon

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=200607101928.k6AJSaHo031519@fire-2.osdl.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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