From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: sfr@canb.auug.org.au, kamalesh@linux.vnet.ibm.com,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, netdev@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] clean up of netif_rx_reschedule() changes in drivers
Date: Mon, 29 Dec 2008 18:19:08 -0800 (PST) [thread overview]
Message-ID: <20081229.181908.214463121.davem@davemloft.net> (raw)
In-Reply-To: <20081229153757.GA2857@localhost.localdomain>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Mon, 29 Dec 2008 10:37:57 -0500
> On Mon, Dec 29, 2008 at 09:41:44PM +1100, Stephen Rothwell wrote:
> > Hi Kamalesh,
> >
> > On Mon, 29 Dec 2008 15:55:29 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> > > greping through the sources for the changes missed out, we have
> > >
> > .
> > .
> > >
> > > Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
...
> Thanks guys, not sure how my patch missed that. I did an allmodconfig build
> that passed successfully. Thanks!
It's very simple, you're not building on powerpc or ARM :-)
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Applied, thanks everyone.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kamalesh@linux.vnet.ibm.com,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] clean up of netif_rx_reschedule() changes in drivers
Date: Mon, 29 Dec 2008 18:19:08 -0800 (PST) [thread overview]
Message-ID: <20081229.181908.214463121.davem@davemloft.net> (raw)
In-Reply-To: <20081229153757.GA2857@localhost.localdomain>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Mon, 29 Dec 2008 10:37:57 -0500
> On Mon, Dec 29, 2008 at 09:41:44PM +1100, Stephen Rothwell wrote:
> > Hi Kamalesh,
> >
> > On Mon, 29 Dec 2008 15:55:29 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> > > greping through the sources for the changes missed out, we have
> > >
> > .
> > .
> > >
> > > Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
...
> Thanks guys, not sure how my patch missed that. I did an allmodconfig build
> that passed successfully. Thanks!
It's very simple, you're not building on powerpc or ARM :-)
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Applied, thanks everyone.
next prev parent reply other threads:[~2008-12-30 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 0:00 linux-next: origin tree build failure Stephen Rothwell
2008-12-29 0:00 ` Stephen Rothwell
2008-12-29 10:25 ` [PATCH] clean up of netif_rx_reschedule() changes in drivers Kamalesh Babulal
2008-12-29 10:25 ` Kamalesh Babulal
2008-12-29 10:41 ` Stephen Rothwell
2008-12-29 10:41 ` Stephen Rothwell
2008-12-29 15:37 ` Neil Horman
2008-12-30 2:19 ` David Miller [this message]
2008-12-30 2:19 ` David Miller
2008-12-30 16:39 ` Neil Horman
2008-12-30 16:39 ` Neil Horman
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=20081229.181908.214463121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 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.