public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: Richard Guy Briggs <rgb@redhat.com>, Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com, Paul Burton <paul.burton@imgtec.com>,
	James Hogan <james.hogan@imgtec.com>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: use current instead of task in syscall_get_arch
Date: Fri, 11 Apr 2014 11:18:27 +0100	[thread overview]
Message-ID: <5347C173.30902@imgtec.com> (raw)
In-Reply-To: <20140411024334.GD24821@madcap2.tricolour.ca>

On 04/11/2014 03:43 AM, Richard Guy Briggs wrote:
> On 14/04/10, Eric Paris wrote:
>> In commit 6e345746 Markos started using task to determine 64bit vs
>> 32bit instead of it being completely CONFIG based.
>>
>> In commit 5e937a9a we dropped the 'task' argument to syscall_get_arch()
>> across the entire system.
>>
>> This obviously results in a build failure when Linus's and the audit
>> tree were merged.  This patch should be applied as part of the merge
>> conflict, as both sides of the merge are correct and the failure happens
>> AT the merge.
>>
>> The fix is simple.  The task is always current.  Use current.
>>
>> Signed-off-by: Eric Paris <eparis@redhat.com>
>> Cc: markos.chandras@imgtec.com
>> Cc: Paul Burton <paul.burton@imgtec.com>
>> Cc: James Hogan <james.hogan@imgtec.com>
>> Cc: linux-mips@linux-mips.org
>
> Signed-off-by: Richard Guy Briggs <rgb@redhat.com>

Looks good to me. Thanks for taking care of that.

Reviewed-by: Markos Chandras <markos.chandras@imgtec.com>

-- 
markos

      reply	other threads:[~2014-04-11 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  2:25 [PATCH] MIPS: use current instead of task in syscall_get_arch Eric Paris
2014-04-11  2:43 ` Richard Guy Briggs
2014-04-11 10:18   ` Markos Chandras [this message]

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=5347C173.30902@imgtec.com \
    --to=markos.chandras@imgtec.com \
    --cc=eparis@redhat.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@imgtec.com \
    --cc=rgb@redhat.com \
    /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