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>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Greg KH <greg@kroah.com>, Ross Cohen <rcohen@snurgle.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 19 (staging/media/go7007)
Date: Mon, 19 Dec 2011 12:38:28 -0800 [thread overview]
Message-ID: <4EEFA0C4.5050107@xenotime.net> (raw)
In-Reply-To: <20111219185556.f07c1f43e28cfd594aaa5fe0@canb.auug.org.au>
On 12/18/2011 11:55 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20111216:
WARNING: modpost: missing MODULE_LICENSE() in drivers/staging/media/go7007/go7007-usb.o
see include/linux/module.h for more information
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-12-19 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 7:55 linux-next: Tree for Dec 19 Stephen Rothwell
2011-12-19 20:32 ` linux-next: Tree for Dec 19 (xen) Randy Dunlap
2011-12-19 20:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-12-19 20:38 ` Randy Dunlap [this message]
2011-12-19 20:44 ` linux-next: Tree for Dec 19 (nfc) Randy Dunlap
2011-12-20 16:39 ` Samuel Ortiz
2011-12-20 20:14 ` Randy Dunlap
2011-12-21 19:57 ` Randy Dunlap
2011-12-21 19:02 ` John W. Linville
2011-12-21 20:20 ` Randy Dunlap
[not found] ` <4EF23A1F.60803-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-12-21 20:42 ` Samuel Ortiz
2011-12-21 21:58 ` Randy Dunlap
2011-12-21 23:35 ` Samuel Ortiz
2011-12-22 1:52 ` Randy Dunlap
2011-12-22 1:03 ` Stephen Rothwell
2011-12-20 1:52 ` linux-next: Tree for Dec 19 Mark Brown
2011-12-20 3:20 ` Stephen Rothwell
2011-12-20 6:39 ` Stephen Rothwell
2011-12-20 11:54 ` Mark Brown
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=4EEFA0C4.5050107@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rcohen@snurgle.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).