All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: fxload patch to set bRequest byte
Date: Wed, 26 Oct 2005 22:49:56 +0000	[thread overview]
Message-ID: <20051026224956.GC13495@kroah.com> (raw)
In-Reply-To: <20051019014259.GD13089@kachi2>

On Sat, Oct 22, 2005 at 09:09:05AM +0200, pix wrote:
> On Thu, Oct 20, 2005 at 03:33:09PM -0700, Greg KH wrote:
> > On Wed, Oct 19, 2005 at 03:42:59AM +0200, pix wrote:
> > > 
> > > i needed this to get the emi26 driver out of the kernel (since it's
> > > being removed in some distributions already for being non-free). 
> > 
> > That's just Debian being anal for no good reason.  Don't give in to
> > them, they are just being foolish :)
> 
> well i think they are just preparing for the inevitable. you can't have
> a kernel claiming to be gpl if it contains code covered by a license
> that is not, by any stretch of the imagination, gpl-compatible.

Um, but that code is not run on the same processor...  Anyway, I don't
want to bring up this age-old argument again.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2005-10-26 22:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  1:42 fxload patch to set bRequest byte pix
2005-10-20 22:33 ` Greg KH
2005-10-22  7:09 ` pix
2005-10-26 22:49 ` Greg KH [this message]

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=20051026224956.GC13495@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.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 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.