From: David Miller <davem@davemloft.net>
To: laurentp@cse-semaphore.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: patches for 2.6.26
Date: Thu, 10 Apr 2008 15:16:16 -0700 (PDT) [thread overview]
Message-ID: <20080410.151616.204291886.davem@davemloft.net> (raw)
In-Reply-To: <200804101720.36975.laurentp@cse-semaphore.com>
From: Laurent Pinchart <laurentp@cse-semaphore.com>
Date: Thu, 10 Apr 2008 17:20:36 +0200
> On Thursday 10 April 2008 16:21, Kumar Gala wrote:
> > Guy's
> >
> > if you have work you want in 2.6.26 related to Freescale PPC's let me
> > know. Ideally you can provide links to the patches in
> > http://patchwork.ozlabs.org/linuxppc/
>
> Could you please add this one ?
>
> fs_enet: Don't call NAPI functions when NAPI is not used.
> http://patchwork.ozlabs.org/linuxppc/patch?id=17055
I kindly request that PPC folks send networking driver patches through
the normal channels so that the networking experts on netdev and
people like Jeff Garzik can review such changes.
In fact this patch here is a bug fix and belongs in the tree right
now, instead of waiting for 2.6.26
next prev parent reply other threads:[~2008-04-10 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 14:21 patches for 2.6.26 Kumar Gala
2008-04-10 15:20 ` Laurent Pinchart
2008-04-10 15:36 ` Kumar Gala
2008-04-10 22:16 ` David Miller [this message]
2008-04-10 22:50 ` Josh Boyer
2008-04-11 11:45 ` Anton Vorontsov
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=20080410.151616.204291886.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.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).