All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Eric Paris <eparis@redhat.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the tip tree with the audit tree
Date: Sat, 27 Sep 2014 20:11:28 +1000	[thread overview]
Message-ID: <20140927201128.3f6a34c7@canb.auug.org.au> (raw)
In-Reply-To: <CALCETrUFHZuhG5qHaJ3yi8P06hLYSo+76y5ZcqXwHahQSUZt-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

Hi Andy,

On Fri, 26 Sep 2014 11:02:27 -0700 Andy Lutomirski <luto@amacapital.net> wrote:
>
> I don't think that more cleanup is possible after all.
> do_audit_syscall_entry may not need to pass the arch parameter to the
> audit code, but it still needs it to choose the set of registers to
> use.

Yes, indeed, I did not look clearly enough :-(

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-27 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24  5:47 linux-next: manual merge of the tip tree with the audit tree Stephen Rothwell
2014-09-24 18:12 ` Andy Lutomirski
2014-09-24 18:14   ` Andy Lutomirski
2014-09-26 18:02 ` Andy Lutomirski
2014-09-27 10:11   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-24  5:38 Stephen Rothwell
2014-09-26 15:01 ` Richard Guy Briggs

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=20140927201128.3f6a34c7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=eparis@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.