From: Jonas Bonn <jonas@southpole.se>
To: Richard Weinberger <richard@nod.at>
Cc: arnd@arndb.de, linux@openrisc.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] OpenRISC: Fix audit_syscall_exit() usage
Date: Wed, 29 Feb 2012 09:48:28 +0100 [thread overview]
Message-ID: <1330505308.2964.24.camel@crucifix> (raw)
In-Reply-To: <4F4DE30B.4060506@nod.at>
On Wed, 2012-02-29 at 09:34 +0100, Richard Weinberger wrote:
> Am 29.02.2012 08:46, schrieb Jonas Bonn:
> >
> > Thanks, Richard. There is, however, already a patch in linux-next that
> > provides this fix.
>
> No problem.
> Why is the fix not in Linus' tree?
I have no good excuse... will send a pull request in short order.
/Jonas
prev parent reply other threads:[~2012-02-29 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:46 [PATCH 1/2] OpenRISC: Fix audit_syscall_exit() usage Richard Weinberger
2012-02-29 0:46 ` [PATCH 2/2] OpenRISC: IRQ: Include module.h Richard Weinberger
2012-02-29 7:49 ` Jonas Bonn
2012-02-29 8:39 ` Richard Weinberger
2012-02-29 8:56 ` Jonas Bonn
2012-02-29 7:46 ` [PATCH 1/2] OpenRISC: Fix audit_syscall_exit() usage Jonas Bonn
2012-02-29 8:34 ` Richard Weinberger
2012-02-29 8:48 ` Jonas Bonn [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=1330505308.2964.24.camel@crucifix \
--to=jonas@southpole.se \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=richard@nod.at \
/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