From mboxrd@z Thu Jan  1 00:00:00 1970
From: wade_farnsworth@mentor.com (Wade Farnsworth)
Date: Tue, 7 Aug 2012 11:46:59 -0700
Subject: Status of patch 7375/1
In-Reply-To: <20120807181359.GK18957@n2100.arm.linux.org.uk>
References: <50214F7D.6040001@mentor.com>
 <20120807175923.GF16877@mudshark.cambridge.arm.com>
 <20120807181359.GK18957@n2100.arm.linux.org.uk>
Message-ID: <502162A3.1020502@mentor.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

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