linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zink, Dan" <dan.zink@hp.com>
To: "Greg KH" <greg@kroah.com>, "Dely Sy" <dlsy@unix-os.sc.intel.com>
Cc: <linux-kernel@vger.kernel.org>,
	<pcihpd-discuss@lists.sourceforge.net>, <tony.luck@intel.com>
Subject: RE: [Pcihpd-discuss] Re: PCI Hot-plug driver patch for 2.5.74 kernel
Date: Thu, 10 Jul 2003 23:22:55 -0500	[thread overview]
Message-ID: <8C91B010B3B7994C88A266E1A72184D301AA0451@cceexc19.americas.cpqcorp.net> (raw)

We've looked at the patch a bit and would prefer that it not
be applied as is.  In particular, it seems to remove proper
detection for features that are in the driver today.  For example,
the decisions that are made off the subsytem ID...

Would it be possible to split this into smaller patches that
each do one particular thing?

Regards,
Dan  

> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com] 
> Sent: Thursday, July 10, 2003 8:39 PM
> To: Dely Sy
> Cc: linux-kernel@vger.kernel.org; 
> pcihpd-discuss@lists.sourceforge.net; tony.luck@intel.com
> Subject: [Pcihpd-discuss] Re: PCI Hot-plug driver patch for 
> 2.5.74 kernel
> 
> 
> Thanks, I'm going to wait to see what the HP/Compaq people 
> have to say about this patch before applying it.
> 
> greg k-h
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book. 
> www.parasoft.com/bulletproofapps1 
> _______________________________________________
> Pcihpd-discuss mailing list Pcihpd-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pcihpd-discuss
> 

             reply	other threads:[~2003-07-11  4:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11  4:22 Zink, Dan [this message]
2003-07-11 16:10 [Pcihpd-discuss] Re: PCI Hot-plug driver patch for 2.5.74 kernel Sy, Dely L
2003-07-11 16:53 ` 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=8C91B010B3B7994C88A266E1A72184D301AA0451@cceexc19.americas.cpqcorp.net \
    --to=dan.zink@hp.com \
    --cc=dlsy@unix-os.sc.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=tony.luck@intel.com \
    /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).