All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: lblnet tree build failure
Date: Wed, 3 Dec 2008 09:51:06 -0500	[thread overview]
Message-ID: <200812030951.06686.paul.moore@hp.com> (raw)
In-Reply-To: <20081203162202.01a3088f.sfr@canb.auug.org.au>

On Wednesday 03 December 2008 12:22:02 am Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> security/smack/smackfs.c: In function 'smk_unlbl_ambient':
> security/smack/smackfs.c:386: warning: passing argument 2 of
> 'netlbl_cfg_map_del' makes integer from pointer without a cast
> security/smack/smackfs.c:386: error: too few arguments to function
> 'netlbl_cfg_map_del'
>
> Caused by commit dc9d06d6226e4855c50961940498427acb4f9866 ("netlabel:
> Update kernel configuration API").
>
> I have dropped the lblnet tree for today.

My apologies (again), I'll get that fixed up today.  Casey, the Smack 
maintainer, and I have been changing things around a fair amount lately 
and it looks like I missed something in the last update.

-- 
paul moore
linux @ hp

  reply	other threads:[~2008-12-03 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  5:22 linux-next: lblnet tree build failure Stephen Rothwell
2008-12-03 14:51 ` Paul Moore [this message]
2008-12-04  0:04   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-16  8:14 Stephen Rothwell
2008-12-16 16:33 ` Paul Moore
2008-12-17  0:04   ` Stephen Rothwell
2008-11-18  4:11 Stephen Rothwell
2008-11-18 14:26 ` Paul Moore
2008-11-18 20:08   ` Stephen Rothwell

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=200812030951.06686.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=linux-next@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 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.