From: Francois Romieu <romieu@fr.zoreil.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, "K.M. Liu" <kmliu@sis.com.tw>
Subject: Re: [PATCH 0/4] Pull request for 'sis190' branch
Date: Thu, 27 Dec 2007 00:17:23 +0100 [thread overview]
Message-ID: <20071226231723.GA4547@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <476703B9.7010604@garzik.org>
Jeff Garzik <jeff@garzik.org> :
[...]
>> Shortlog
>> --------
>>
>> Francois Romieu (4):
>> sis190: add cmos ram access code for the SiS19x/968 chipset pair
>> sis190: remove duplicate INIT_WORK
>> sis190: mdio operation failure is not correctly detected
>> sis190: scheduling while atomic error
>
> pulled into #upstream
Imho no owner of a 968 south bridge will be able to use his integrated
network device as long as "sis190: add cmos ram access code ..." is
not included upstream. Waiting for 2.6.25 means no hardware support
before march 2008.
--
Ueimor
prev parent reply other threads:[~2007-12-26 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 22:27 [PATCH 0/4] Pull request for 'sis190' branch Francois Romieu
2007-12-10 22:29 ` [PATCH 1/4] sis190: add cmos ram access code for the SiS19x/968 chipset pair Francois Romieu
2007-12-10 22:30 ` [PATCH 2/4] sis190: remove duplicate INIT_WORK Francois Romieu
2007-12-10 22:31 ` [PATCH 3/4] sis190: mdio operation failure is not correctly detected Francois Romieu
2007-12-10 22:31 ` [PATCH 4/4] sis190: scheduling while atomic error Francois Romieu
2007-12-17 23:18 ` [PATCH 0/4] Pull request for 'sis190' branch Jeff Garzik
2007-12-26 23:17 ` Francois Romieu [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=20071226231723.GA4547@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=kmliu@sis.com.tw \
--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).