From: wade_farnsworth@mentor.com (Wade Farnsworth)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of patch 7375/1
Date: Tue, 7 Aug 2012 11:46:59 -0700 [thread overview]
Message-ID: <502162A3.1020502@mentor.com> (raw)
In-Reply-To: <20120807181359.GK18957@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Tue, Aug 07, 2012 at 06:59:23PM +0100, Will Deacon wrote:
>> Wade,
>>
>> On Tue, Aug 07, 2012 at 06:25:17PM +0100, Wade Farnsworth wrote:
>>> I'm inquiring regarding the status of patch 7375/1 in the patch tracker:
>>>
>>> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7375/1
>>>
>>> The other two patches in the series were approved and are now in Linus's
>>> tree. However this one never received approval, nor any comments
>>> indicating that it was rejected. What is the status of this patch? Is
>>> there anything I can do to help move it forward?
>>
>> There have been a bunch of fixes to the audit, syscall tracing and signal
>> handling code so you'll probably need to rebase your patch on top of
>> 3.6-rc1. I think I CC'd you at the time (at least, that was my intention!).
>
> Yes, it became impossible to apply when all the syscall/audit fixes went
> in, which was more important than adding a new feature.
>
> I think the audit/syscall fixes have settled now, so as Will says...
>
>> Would you be able to do that and send it to the list again please?
>
> Thanks.
Fair enough. I'll see about on rebasing the patch against 3.6-rc1.
Thanks for the quick response.
Wade
prev parent reply other threads:[~2012-08-07 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 17:25 Status of patch 7375/1 Wade Farnsworth
2012-08-07 17:59 ` Will Deacon
2012-08-07 18:13 ` Russell King - ARM Linux
2012-08-07 18:46 ` Wade Farnsworth [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=502162A3.1020502@mentor.com \
--to=wade_farnsworth@mentor.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.