netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jesse Huang" <jesse@icplus.com.tw>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<akpm@osdl.org>
Subject: Re: How about current IP100A status? 10/31/2006
Date: Thu, 2 Nov 2006 15:56:08 +0800	[thread overview]
Message-ID: <003501c6fe54$5b475fb0$4964a8c0@icplus.com.tw> (raw)
In-Reply-To: 4549803D.5020302@pobox.com

Dear Jeff:

    Thanks for your help. We are happy to see new version of
our driver will be support in the new kernel.

Best Regards,
Jesse Huang


----- Original Message ----- 
From: "Jeff Garzik" <jgarzik@pobox.com>
To: "Jesse Huang" <jesse@icplus.com.tw>
Cc: <linux-kernel@vger.kernel.org>; <netdev@vger.kernel.org>;
<akpm@osdl.org>
Sent: Thursday, November 02, 2006 1:21 PM
Subject: Re: How about current IP100A status? 10/31/2006


Jesse Huang wrote:
> Dear All:
>
> How about current IP100A, sundance.c status? Should it be put into kernel
or
> not?
> Is there any sentence should I need to modify?

It's in my queue.  We are in a bug fix-only cycle right now, so it has
been a bit lower priority, but I will queue it for 2.6.20.

Jeff

  reply	other threads:[~2006-11-02  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002101c6fe3e$369ca1e0$4964a8c0@icplus.com.tw>
2006-11-02  5:21 ` How about current IP100A status? 10/31/2006 Jeff Garzik
2006-11-02  7:56   ` Jesse Huang [this message]
2006-10-14 19:57 [PATCH 5/5] Solve host error problem in low performance embedded system when continune down and up Jesse Huang
2006-10-31  5:39 ` How about current IP100A status? 10/31/2006 Jesse Huang

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='003501c6fe54$5b475fb0$4964a8c0@icplus.com.tw' \
    --to=jesse@icplus.com.tw \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 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).