All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Richard Guy Briggs <rgb@redhat.com>
Subject: Re: linux-next: build failure after merge of the audit tree
Date: Wed, 06 Nov 2013 11:54:57 -0500	[thread overview]
Message-ID: <1383756897.28218.66.camel@flatline.rdu.redhat.com> (raw)
In-Reply-To: <20131106172734.28986a5907009f84aead4e8b@canb.auug.org.au>

On Wed, 2013-11-06 at 17:27 +1100, Stephen Rothwell wrote:
> Hi Eric,
> 
> After merging the audit tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> kernel/auditsc.c: In function 'audit_set_loginuid':
> kernel/auditsc.c:2003:15: error: incompatible types when assigning to type 'kuid_t' from type 'int'
>   oldsessionid = audit_get_sessionid(current);
>                ^
> kernel/auditsc.c:2016:2: error: incompatible type for argument 3 of 'audit_log_set_loginuid'
>   audit_log_set_loginuid(oldloginuid, loginuid, oldsessionid, sessionid, rc);
>   ^
> kernel/auditsc.c:1967:13: note: expected 'unsigned int' but argument is of type 'kuid_t'
>  static void audit_log_set_loginuid(kuid_t koldloginuid, kuid_t kloginuid,
>              ^
> 
> Caused by commit da0a610497ce ("audit: loginuid functions coding style").
> 
> I have used the version of the audit tree from next-20131105 for today.
> 

Should be fixed for tomorrow.  Thank you.


  reply	other threads:[~2013-11-06 16:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  6:27 linux-next: build failure after merge of the audit tree Stephen Rothwell
2013-11-06 16:54 ` Eric Paris [this message]
2014-04-22  6:22 Stephen Rothwell
2014-04-22  6:22 ` Stephen Rothwell
2014-04-22 15:56 ` Richard Guy Briggs
2014-04-22 15:56   ` Richard Guy Briggs
2014-04-22 16:32 ` Eric Paris
2014-04-22 16:32   ` Eric Paris
2014-04-22 21:27   ` Stephen Rothwell
2014-04-22 21:27     ` 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=1383756897.28218.66.camel@flatline.rdu.redhat.com \
    --to=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rgb@redhat.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 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.