All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Abhay_Salunke@Dell.com
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org, akpm@osdl.org,
	Matt_Domsch@Dell.com
Subject: Re: [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver
Date: Tue, 7 Jun 2005 08:01:30 -0700	[thread overview]
Message-ID: <20050607150130.GA14362@kroah.com> (raw)
In-Reply-To: <367215741E167A4CA813C8F12CE0143B3ED3B0@ausx2kmpc115.aus.amer.dell.com>

On Tue, Jun 07, 2005 at 09:47:47AM -0500, Abhay_Salunke@Dell.com wrote:
> > Why not fix the firmware_class.c code now?  :)
> I am working on a solution for this; so yes, I will submit a patch to
> enhance firmware_class.c code.

Good.

> Mean while the driver sent earlier is tested and working on current
> version of 2.6 kernel and we have tested it with various distros based
> on 2.6 kernel. Changing the kernel and making the driver dependent on
> the new code will make the driver not work on the current kernels which
> the users have. 

Drivers are tightly bound to kernel versions.  Nothing new there.

> This will make driver non functional on current 2.6 kernels and will be
> an issue if users don't want to upgrade their kernels but just want the
> driver to update BIOS.

Then persuade the distros to accept your current version.  That's not
our issue :)

thanks,

greg k-h

  reply	other threads:[~2005-06-07 15:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 14:47 [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver Abhay_Salunke
2005-06-07 15:01 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-06 20:22 Abhay_Salunke
2005-06-06 20:35 ` Greg KH
2005-06-06 20:01 Abhay_Salunke
2005-06-06 20:12 ` Greg KH
2005-06-06 18:54 Abhay_Salunke
2005-06-06 19:22 ` Greg KH
2005-06-06 16:27 Abhay_Salunke
2005-06-06 18:16 ` Greg KH
2005-06-03 19:57 Abhay_Salunke
2005-06-03 20:33 ` Greg KH
2005-06-03 19:00 Abhay_Salunke
2005-06-03 19:29 ` Greg KH
2005-06-03 13:30 Abhay_Salunke
2005-06-03 16:53 ` Marcel Holtmann
2005-06-03 18:03 ` Greg KH
2005-06-02 22:25 Abhay_Salunke
2005-06-02 22:45 ` Marcel Holtmann
2005-06-02 22:50 ` Andrew Morton
2005-06-03  5:19 ` Greg KH
2005-05-23 15:36 Abhay_Salunke
2005-05-23 15:50 ` Greg KH

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=20050607150130.GA14362@kroah.com \
    --to=greg@kroah.com \
    --cc=Abhay_Salunke@Dell.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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.