From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH -queue] MIPS/net: fix au1000_eth.c build and warnings
Date: Wed, 17 Feb 2010 15:58:09 +0100 [thread overview]
Message-ID: <20100217145809.GK1561@linux-mips.org> (raw)
In-Reply-To: <1266263017-6874-1-git-send-email-manuel.lauss@gmail.com>
On Mon, Feb 15, 2010 at 08:43:37PM +0100, Manuel Lauss wrote:
> - buildfix: DECLARE_MAC_BUF was removed recently.
> - remove various warnings spit out during build
>
> Only compile-tested.
>
> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> ---
> Hi Ralf! Please fold this into the patch titled
> "NET: au1000-eth: convert to platform_driver model"
> in mips-queue, thank you!
Done - but as this is a net patch it should have been cc'ed to netdev /
DaveM as well ...
Ralf
next prev parent reply other threads:[~2010-02-17 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 19:43 [PATCH -queue] MIPS/net: fix au1000_eth.c build and warnings Manuel Lauss
2010-02-17 14:58 ` Ralf Baechle [this message]
2010-02-17 15:03 ` Florian Fainelli
2010-02-17 16:35 ` Ralf Baechle
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=20100217145809.GK1561@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=manuel.lauss@googlemail.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