From: Jeff Garzik <jeff@garzik.org>
To: Francois Romieu <romieu@fr.zoreil.com>
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: Mon, 17 Dec 2007 18:18:17 -0500 [thread overview]
Message-ID: <476703B9.7010604@garzik.org> (raw)
In-Reply-To: <20071210222732.GA8675@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Please pull from branch 'sis190' in repository
>
> git://git.kernel.org/pub/scm/linux/kernel/git/romieu/netdev-2.6.git sis190
>
> to get the changes below.
>
> Distance from 'upstream-linus' (7962024e9d16e9349d76b553326f3fa7be64305e)
> -------------------------------------------------------------------------
>
> c27e14e508664471b8e44ef1f81ec080213ea314
> 348de67fe200e25d8cb80cff35642192436cfeda
> 004a22d03d62cd08e5287273a5143447db009cd0
> 14deb44ffe7220be2de697d616f28cce17e72297
>
> Diffstat
> --------
>
> drivers/net/sis190.c | 21 ++++++++++-----------
> 1 files changed, 10 insertions(+), 11 deletions(-)
>
> 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
next prev parent reply other threads:[~2007-12-17 23:18 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 ` Jeff Garzik [this message]
2007-12-26 23:17 ` [PATCH 0/4] Pull request for 'sis190' branch Francois Romieu
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=476703B9.7010604@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=kmliu@sis.com.tw \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 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.