From: Krzysztof Halasa <khc@pm.waw.pl>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
davem@davemloft.net, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] wan: pci200syn needs capability.h
Date: Tue, 13 Oct 2009 19:19:47 +0200 [thread overview]
Message-ID: <m33a5n5hzg.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20091013100016.3c9bfad7.randy.dunlap@oracle.com> (Randy Dunlap's message of "Tue, 13 Oct 2009 10:00:16 -0700")
Randy Dunlap <randy.dunlap@oracle.com> writes:
> Driver is missing header file capability.h:
>
> drivers/net/wan/pci200syn.c:212: error: implicit declaration of function 'capable'
> drivers/net/wan/pci200syn.c:212: error: 'CAP_NET_ADMIN' undeclared (first use in this function)
Thanks, but I think a patch for a bunch of WAN drivers has been already
posted.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-10-13 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 5:23 linux-next: Tree for October 13 Stephen Rothwell
2009-10-13 10:06 ` [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC_PROTECT Kamalesh Babulal
2009-10-13 10:33 ` Martin Schwidefsky
2009-10-13 10:57 ` Kamalesh Babulal
2009-10-13 16:28 ` [BUILD_FAILURE] next-20091013 s390x - build breaks SCLP VT220 terminal driver Kamalesh Babulal
2009-10-14 9:02 ` Martin Schwidefsky
2009-10-14 10:45 ` Martin Schwidefsky
2009-10-14 16:02 ` Kamalesh Babulal
2009-10-13 17:00 ` [PATCH] wan: pci200syn needs capability.h Randy Dunlap
2009-10-13 17:19 ` Krzysztof Halasa [this message]
2009-10-13 17:01 ` [PATCH] whci: fix type and format warnings Randy Dunlap
[not found] ` <20091013100128.0f06d67c.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-10-13 17:51 ` David Vrabel
2009-10-13 18:07 ` 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=m33a5n5hzg.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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