From: Valerie Henson <val_henson@linux.intel.com>
To: Kyle McMartin <kyle@parisc-linux.org>
Cc: Andrew Morton <akpm@osdl.org>,
grundler@parisc-linux.org, netdev@vger.kernel.org,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [git patches] tulip fixes from parisc-linux
Date: Mon, 31 Jul 2006 20:10:25 -0700 [thread overview]
Message-ID: <20060801031024.GF11415@goober> (raw)
In-Reply-To: <20060730185456.GA17066@tachyon.int.mcmartin.ca>
On Sun, Jul 30, 2006 at 02:54:56PM -0400, Kyle McMartin wrote:
> On Sun, Jul 30, 2006 at 11:35:32AM -0700, Andrew Morton wrote:
> > hm. A couple of those patches have been futzing around in -mm for over a
> > year and have been nacked by Jeff and are a regular source of grumpygrams.
> > I've been sitting on them in the pathetic hope that someone will one day
> > get down and address the bugs which they fix in an acceptable fashion,
> > whatever that is.
> >
>
> Jeff/Val seemed willing to merge the fixes as they stood. parisc-linux
> merged Francois' tulip workqueue patch some time ago, and have been
> running with it since without issue. This defers the tulip_select_media
> work to process context, and so should be less of an issue.
Hey Kyle,
Thanks for splitting these out. Could you do us a favor and post the
patches themselves? I'm not the only one who doesn't use git, and it
will be a lot less confusing if we can directly ack the patches in
email instead of referring to them third-hand. Thanks,
-VAL
next prev parent reply other threads:[~2006-08-01 3:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 22:54 [git patches] tulip fixes from parisc-linux Kyle McMartin
2006-07-30 0:43 ` [parisc-linux] " Grant Grundler
2006-07-30 16:56 ` Kyle McMartin
2006-07-30 18:35 ` Andrew Morton
2006-07-30 18:54 ` Kyle McMartin
2006-07-30 22:56 ` Jeff Garzik
2006-08-01 3:10 ` Valerie Henson [this message]
2006-07-30 22:55 ` 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=20060801031024.GF11415@goober \
--to=val_henson@linux.intel.com \
--cc=akpm@osdl.org \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=netdev@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.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).