From: Paul Moore <paul@paul-moore.com>
To: Olof Johansson <olof@lixom.net>
Cc: David Miller <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>
Subject: Re: netlabel build warning...
Date: Sat, 09 Aug 2014 12:23:18 -0400 [thread overview]
Message-ID: <efdc8ee2-f7ea-4601-9118-88595281bc5d@email.android.com> (raw)
In-Reply-To: <CAOesGMgCDd9+=x9M=sP+rRgJOKrT+SC7VNw_X_mj5WZtiPxW1g@mail.gmail.com>
On August 9, 2014 12:19:02 PM EDT, Olof Johansson <olof@lixom.net> wrote:
>On Wed, Aug 6, 2014 at 4:23 PM, Paul Moore <paul@paul-moore.com> wrote:
>> On Wed, Aug 6, 2014 at 5:55 PM, David Miller <davem@davemloft.net>
>wrote:
>>>
>>> Please add inline to the nop versions of these helpers, thanks:
>>>
>>> include/net/netlabel.h:527:12: warning: ‘netlbl_catmap_setlong’
>defined but not used [-Wunused-function]
>>> include/net/netlabel.h:527:12: warning: ‘netlbl_catmap_setlong’
>defined but not used [-Wunused-function]
>>
>> I posted a fix to the SELinux list yesterday (link below); in
>> retrospect, I should have CC'd netdev, my apologies. As soon as -rc1
>> is released and linux-next opens for business I'll be pushing the
>> patch to the SELinux #next branch.
>>
>> * http://marc.info/?l=selinux&m=140726989229890&w=2
>
>Why hold it off for 3.18? It's small and trivial and removes a
>warning, might as well go in sooner.
>
>
>-Olof
I sent a pull request to Linus yesterday and CC'd netdev.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2014-08-09 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 21:55 netlabel build warning David Miller
2014-08-06 23:23 ` Paul Moore
2014-08-09 16:19 ` Olof Johansson
2014-08-09 16:23 ` Paul Moore [this message]
2014-08-09 16:27 ` Paul Moore
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=efdc8ee2-f7ea-4601-9118-88595281bc5d@email.android.com \
--to=paul@paul-moore.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/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