All of lore.kernel.org
 help / color / mirror / Atom feed
From: behanw@converseincode.com (Behan Webster)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Tue, 26 Aug 2014 21:26:37 -0700	[thread overview]
Message-ID: <53FD5DFD.80405@converseincode.com> (raw)
In-Reply-To: <20140826141608.GT23445@arm.com>

On 08/26/14 07:16, Will Deacon wrote:
> Hi Behan,
>
> On Fri, Aug 01, 2014 at 05:11:59AM +0100, Behan Webster wrote:
>> On 07/31/14 03:33, Will Deacon wrote:
>>> On Thu, Jul 31, 2014 at 12:57:25AM +0100, behanw at converseincode.com wrote:
>>>> From: Behan Webster <behanw@converseincode.com>
>>>>
>>>> This patch set moves from using locally defined named registers to access the
>>>> stack pointer to using a globally defined named register. This allows the code
>>>> to work both with gcc and clang.
>>>>
>>>> The LLVMLinux project aims to fully build the Linux kernel using both gcc and
>>>> clang (the C front end for the LLVM compiler infrastructure project).
>>>>
>>>> Behan Webster (4):
>>>>     arm64: LLVMLinux: Add current_stack_pointer() for arm64
>>>>     arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk
>>>>     arm64: LLVMLinux: Calculate current_thread_info from
>>>>       current_stack_pointer
>>>>     arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c
>>> Once Andreas's comments have been addressed:
>>>
>>>     Acked-by: Will Deacon <will.deacon@arm.com>
>>>
>>> Please can you send a new series after the merge window?
>> Pity. I was hoping to get it in this merge window.
>>
>> However, will resubmit for 3.18.
> Any chance of a v2 for this series, please? If you address the comments
> pending for v1, I think it's good to merge.
Sure thing. 2 more named register patches added. Look for them at the 
end of the new patch series.

I kept missing you in Chicago. I was hoping to say "hi".

Behan

-- 
Behan Webster
behanw at converseincode.com

WARNING: multiple messages have this Message-ID (diff)
From: Behan Webster <behanw@converseincode.com>
To: Will Deacon <will.deacon@arm.com>
Cc: "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	"k.khlebnikov@samsung.com" <k.khlebnikov@samsung.com>,
	"olof@lixom.net" <olof@lixom.net>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"takahiro.akashi@linaro.org" <takahiro.akashi@linaro.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
Date: Tue, 26 Aug 2014 21:26:37 -0700	[thread overview]
Message-ID: <53FD5DFD.80405@converseincode.com> (raw)
In-Reply-To: <20140826141608.GT23445@arm.com>

On 08/26/14 07:16, Will Deacon wrote:
> Hi Behan,
>
> On Fri, Aug 01, 2014 at 05:11:59AM +0100, Behan Webster wrote:
>> On 07/31/14 03:33, Will Deacon wrote:
>>> On Thu, Jul 31, 2014 at 12:57:25AM +0100, behanw@converseincode.com wrote:
>>>> From: Behan Webster <behanw@converseincode.com>
>>>>
>>>> This patch set moves from using locally defined named registers to access the
>>>> stack pointer to using a globally defined named register. This allows the code
>>>> to work both with gcc and clang.
>>>>
>>>> The LLVMLinux project aims to fully build the Linux kernel using both gcc and
>>>> clang (the C front end for the LLVM compiler infrastructure project).
>>>>
>>>> Behan Webster (4):
>>>>     arm64: LLVMLinux: Add current_stack_pointer() for arm64
>>>>     arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk
>>>>     arm64: LLVMLinux: Calculate current_thread_info from
>>>>       current_stack_pointer
>>>>     arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c
>>> Once Andreas's comments have been addressed:
>>>
>>>     Acked-by: Will Deacon <will.deacon@arm.com>
>>>
>>> Please can you send a new series after the merge window?
>> Pity. I was hoping to get it in this merge window.
>>
>> However, will resubmit for 3.18.
> Any chance of a v2 for this series, please? If you address the comments
> pending for v1, I think it's good to merge.
Sure thing. 2 more named register patches added. Look for them at the 
end of the new patch series.

I kept missing you in Chicago. I was hoping to say "hi".

Behan

-- 
Behan Webster
behanw@converseincode.com


  reply	other threads:[~2014-08-27  4:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 23:57 [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw at converseincode.com
2014-07-30 23:57 ` behanw
2014-07-30 23:57 ` [PATCH 1/4] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-07-30 23:57   ` behanw
2014-07-30 23:57 ` [PATCH 2/4] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-07-30 23:57   ` behanw
2014-07-30 23:57 ` [PATCH 3/4] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-07-30 23:57   ` behanw
2014-07-31  5:31   ` Andreas Färber
2014-07-31  5:31     ` Andreas Färber
2014-07-31 16:04     ` Behan Webster
2014-07-31 16:04       ` Behan Webster
2014-07-30 23:57 ` [PATCH 4/4] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-07-30 23:57   ` behanw
2014-07-31  0:11 ` [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Olof Johansson
2014-07-31  0:11   ` Olof Johansson
2014-07-31 10:33 ` Will Deacon
2014-07-31 10:33   ` Will Deacon
2014-07-31 15:39   ` Olof Johansson
2014-07-31 15:39     ` Olof Johansson
2014-07-31 15:48     ` Will Deacon
2014-07-31 15:48       ` Will Deacon
2014-07-31 15:52       ` Olof Johansson
2014-07-31 15:52         ` Olof Johansson
2014-08-01  4:11   ` Behan Webster
2014-08-01  4:11     ` Behan Webster
2014-08-26 14:16     ` Will Deacon
2014-08-26 14:16       ` Will Deacon
2014-08-27  4:26       ` Behan Webster [this message]
2014-08-27  4:26         ` Behan Webster
2014-08-27  4:29       ` [PATCH V2 0/6] " behanw at converseincode.com
2014-08-27  4:29         ` behanw
2014-08-27  4:29         ` [PATCH V2 1/6] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-08-27  4:29           ` behanw
2014-08-27  4:29         ` [PATCH V2 2/6] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-08-27  4:29           ` behanw
2014-08-27  4:29         ` [PATCH V2 3/6] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-08-27  4:29           ` behanw
2014-08-27  4:29         ` [PATCH V2 4/6] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-08-27  4:29           ` behanw
2014-08-27  4:29         ` [PATCH V2 5/6] arm64: LLVMLinux: Use global stack register variable for aarch64 behanw at converseincode.com
2014-08-27  4:29           ` behanw
2014-08-27  4:29         ` [PATCH V2 6/6] arm64: LLVMLinux: Use global stack pointer in return_address() behanw at converseincode.com
2014-08-27  4:29           ` behanw

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=53FD5DFD.80405@converseincode.com \
    --to=behanw@converseincode.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.