From: David Miller <davem@davemloft.net>
To: zajec5@gmail.com
Cc: linux@roeck-us.net, ralf@linux-mips.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [RFC PATCH] bgmac: Fix build error seen if BCM47XX is not configured
Date: Wed, 15 Apr 2015 17:18:05 -0400 (EDT) [thread overview]
Message-ID: <20150415.171805.1957066097252829921.davem@davemloft.net> (raw)
In-Reply-To: <CACna6rwPYP0FV60v9ey0uV=3eU_8SZ4t+WoZCtiDHHeCLiM3Dg@mail.gmail.com>
From: Rafał Miłecki <zajec5@gmail.com>
Date: Wed, 15 Apr 2015 22:21:49 +0200
> I guess the decisions depends on
> a) time needed for David to revert fc300dc & send pull request
> vs.
> b) time needed for Ralf to send pull request
Let's just wait for Ralf's stuff to hit Linus's tree.
prev parent reply other threads:[~2015-04-15 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 20:05 [RFC PATCH] bgmac: Fix build error seen if BCM47XX is not configured Guenter Roeck
2015-04-15 20:21 ` Rafał Miłecki
2015-04-15 20:46 ` Guenter Roeck
2015-04-15 21:18 ` 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=20150415.171805.1957066097252829921.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=zajec5@gmail.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).