From: Andrew Morton <akpm@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: torvalds@osdl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] e1000 fixes
Date: Wed, 18 Jan 2006 14:11:18 -0800 [thread overview]
Message-ID: <20060118141118.78767e3d.akpm@osdl.org> (raw)
In-Reply-To: <20060118212449.GA13260@havoc.gtf.org>
Jeff Garzik <jgarzik@pobox.com> wrote:
>
> Let's see how this goes... if there are further problems, I'll just
> revert the entire thing, and push these changes (and the previous set)
> into upstream-2.6.17 branch.
>
> I don't mind them updating the defconfig files, even though most people
> are too slack to worry about it, since its pretty clear the default
> choice.
>
>
> Please pull from 'upstream-fixes' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
These patches fix e1000 for me, thanks.
next parent reply other threads:[~2006-01-18 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060118212449.GA13260@havoc.gtf.org>
2006-01-18 22:11 ` Andrew Morton [this message]
2007-04-27 17:06 [git patches] e1000 fixes Jeff Garzik
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=20060118141118.78767e3d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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