All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Marc Vertes <marc.vertes@sigfox.com>,
	linux-watchdog@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 28 (via_wdt)
Date: Fri, 06 Jan 2012 18:48:49 -0800	[thread overview]
Message-ID: <4F07B291.4040608@xenotime.net> (raw)
In-Reply-To: <20111228175751.GA14460@infomag.iguana.be>

On 12/28/2011 09:57 AM, Wim Van Sebroeck wrote:
> Hi Randi,
> 
>> via_wdt needs a MODULE_LICENSE():
>>
>> WARNING: modpost: missing MODULE_LICENSE() in drivers/watchdog/via_wdt.o
>> see include/linux/module.h for more information
> 
> Fixed.

Not yet in linux-next ??

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2012-01-07  2:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  9:18 linux-next: Tree for Dec 28 Stephen Rothwell
2011-12-28 18:12 ` linux-next: Tree for Dec 28 (via_wdt) Randy Dunlap
2011-12-28 17:57   ` Wim Van Sebroeck
2012-01-07  2:48     ` Randy Dunlap [this message]
2012-01-07 10:20       ` Wim Van Sebroeck
2011-12-28 20:24 ` linux-next: Tree for Dec 28 (fs-writeback) Randy Dunlap
2011-12-28 21:09 ` linux-next: Tree for Dec 28 (gfs2) Randy Dunlap
2012-01-03 11:17   ` [Cluster-devel] " Steven Whitehouse
2012-01-03 11:17     ` Steven Whitehouse
2011-12-28 21:19 ` linux-next: Tree for Dec 28 (nfnetlink) Randy Dunlap
2011-12-28 20:33   ` David Miller
2011-12-29  1:03     ` Pablo Neira Ayuso
2011-12-29 18:53       ` Randy Dunlap
2011-12-29 19:39         ` David Miller
2011-12-28 21:24 ` linux-next: Tree for Dec 28 (irqdomain.c) Randy Dunlap

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=4F07B291.4040608@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=marc.vertes@sigfox.com \
    --cc=sfr@canb.auug.org.au \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.