qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bill C. Riemers" <docbill@freeshell.org>
To: dragoran <drago01@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] merging kqemu into mainline kernel?
Date: Thu, 16 Aug 2007 11:00:35 -0400	[thread overview]
Message-ID: <46C46693.1020307@freeshell.org> (raw)
In-Reply-To: <46C448DA.70303@gmail.com>

dragoran wrote:
> Bill C. Riemers wrote:
>> You don't need to compile kqemu into the kernel.  When I install
>> dkms-kqemu from freshrpms, I do NOT rebuild my kernel.  I am fairly
>> certain with Fedora's new policy for extras, there would not be much
>> of a problem getting it added to Fedora.  For that matter, it could
>> probably get added into the new Enterprise Extra's repository as
>> well.  However, someone would need to volunteer to maintain the package.
> no thats not true fedora want to change the policy about out of tree
> modules the want to drop all kmod-* packages and only allow modules
> into the kernel rpm that are upstream or about to get merged upstream.
> anyway why has kqemu to be a out of tree module?
It looks like you are right.  Apparently the plan is to move the
acceptance of kernel modules to kernel maintainers.  For the most part,
they only want to accept very cleanly written modules that are likely to
be integrated into the kernel.  Since "kqemu" is viewed as a solution
only for obsolete hardware, that is not likely to happen.  It is a shame
too, because "kqemu" provides a quality working solution for most of the
hardware still in use today.

Bill

  parent reply	other threads:[~2007-08-16 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 15:16 [Qemu-devel] merging kqemu into mainline kernel? dragoran
2007-08-04 16:26 ` Ricardo Almeida
2007-08-04 17:04   ` dragoran
2007-08-16 12:42     ` Bill C. Riemers
2007-08-16 12:53       ` dragoran
2007-08-16 13:49         ` Paul Brook
2007-08-16 14:02           ` Leonardo Reiter
2007-08-16 14:31             ` Paul Brook
2007-08-16 19:05               ` Christian MICHON
2007-08-16 19:51                 ` Ed Swierk
2007-08-16 15:01           ` Jernej Simonèiè
2007-08-16 15:13             ` Daniel P. Berrange
2007-08-16 15:15           ` Luke -Jr
2007-08-16 15:00         ` Bill C. Riemers [this message]
2007-08-17 12:44           ` dragoran
2007-08-17 13:19             ` Sunil Amitkumar Janki

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=46C46693.1020307@freeshell.org \
    --to=docbill@freeshell.org \
    --cc=drago01@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).