From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: netdev@vger.kernel.org, jwboyer@linux.vnet.ibm.com,
galak@kernel.crashing.org, subrata@linux.vnet.ibm.com,
Linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
greg@kroah.com, sachinp@linux.vnet.ibm.com, sfr@canb.auug.org.au
Subject: Re: [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c]
Date: Sat, 11 Apr 2009 02:44:36 -0700 (PDT) [thread overview]
Message-ID: <20090411.024436.40931952.davem@davemloft.net> (raw)
In-Reply-To: <20090410015614.GA5781@orion>
From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Fri, 10 Apr 2009 05:56:14 +0400
> Subject: [PATCH] ibm_newemac: convert to netdev_ops
>
>
> Reported-by: Subrata Modak <subrata@linux.vnet.ibm.com>
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
Applied.
prev parent reply other threads:[~2009-04-11 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:52 [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c] Subrata Modak
2009-04-09 13:57 ` [BUILD FAILURE 05] Next April 9 : PPC64 randconfig [drivers/net/wan/wanxlfw.inc] Subrata Modak
2009-04-09 14:51 ` Geert Uytterhoeven
2009-04-09 15:24 ` [BUILD FAILURE 06] Next April 9 : PPC64 randconfig [drivers/usb/musb/musb_core.c] Subrata Modak
2009-04-09 15:24 ` [BUILD FAILURE 07] Next April 9 : PPC64 randconfig [drivers/scsi/aha1542.o] Subrata Modak
2009-04-09 15:28 ` [BUILD FAILURE 08] Next April 9 : PPC64 randconfig [drivers/net/pasemi_mac_driver.ko] Subrata Modak
2009-04-09 15:34 ` [BUILD FAILURE 09] Next April 9 : PPC64 randconfig [drivers/char/hvcs.ko] Subrata Modak
2009-04-09 14:28 ` [BUILD FAILURE 04] Next April 9 : PPC64 randconfig [drivers/net/ibm_newemac/core.c] Kumar Gala
2009-04-09 14:31 ` Josh Boyer
2009-04-10 1:56 ` Alexander Beregalov
2009-04-11 9:44 ` David Miller [this message]
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=20090411.024436.40931952.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Linuxppc-dev@ozlabs.org \
--cc=a.beregalov@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.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 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).