From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 22 (netdev/stmmac)
Date: Thu, 22 Dec 2011 17:37:09 -0800 [thread overview]
Message-ID: <4EF3DB45.30401@xenotime.net> (raw)
In-Reply-To: <20111222172039.dc704e5bbfc3d91a844897b3@canb.auug.org.au>
On 12/21/2011 10:20 PM, Stephen Rothwell wrote:
> Hi all,
>
> This will probably be the last linux-next tree until the new year (unless
> I get exceedingly bored :-)).
goody :)
WARNING: modpost: missing MODULE_LICENSE() in drivers/net/ethernet/stmicro/stmmac/stmmac.o
see include/linux/module.h for more information
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next parent reply other threads:[~2011-12-23 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111222172039.dc704e5bbfc3d91a844897b3@canb.auug.org.au>
2011-12-23 1:37 ` Randy Dunlap [this message]
2011-12-23 10:18 ` linux-next: Tree for Dec 22 (netdev/stmmac) Giuseppe CAVALLARO
2011-12-23 10:31 ` [net-next] stmmac: fix missing module license in the main Giuseppe CAVALLARO
2011-12-23 11:16 ` Giuseppe CAVALLARO
2011-12-23 19:21 ` David Miller
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=4EF3DB45.30401@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).