All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, rdunlap@infradead.org,
	bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
	guoren@kernel.org, dfustini@baylibre.com,
	linux-next@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH] riscv: Require FRAME_POINTER for some configurations
Date: Wed, 23 Aug 2023 20:10:22 +0000	[thread overview]
Message-ID: <169282142292.4166.3281543334488200075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230823082845.354839-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 23 Aug 2023 10:28:45 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> Some V configurations implicitly turn on '-fno-omit-frame-pointer',
> but leaving FRAME_POINTER disabled. This makes it hard to reason about
> the FRAME_POINTER config, and also triggers build failures introduced
> in by the commit in the Fixes: tag.
> 
> [...]

Here is the summary with links:
  - riscv: Require FRAME_POINTER for some configurations
    https://git.kernel.org/riscv/c/9f944d2e0ab3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, rdunlap@infradead.org,
	bjorn@rivosinc.com, linux-kernel@vger.kernel.org,
	guoren@kernel.org, dfustini@baylibre.com,
	linux-next@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH] riscv: Require FRAME_POINTER for some configurations
Date: Wed, 23 Aug 2023 20:10:22 +0000	[thread overview]
Message-ID: <169282142292.4166.3281543334488200075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230823082845.354839-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 23 Aug 2023 10:28:45 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> Some V configurations implicitly turn on '-fno-omit-frame-pointer',
> but leaving FRAME_POINTER disabled. This makes it hard to reason about
> the FRAME_POINTER config, and also triggers build failures introduced
> in by the commit in the Fixes: tag.
> 
> [...]

Here is the summary with links:
  - riscv: Require FRAME_POINTER for some configurations
    https://git.kernel.org/riscv/c/9f944d2e0ab3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-08-23 20:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  8:28 [PATCH] riscv: Require FRAME_POINTER for some configurations Björn Töpel
2023-08-23  8:28 ` Björn Töpel
2023-08-23  8:49 ` Björn Töpel
2023-08-23  8:49   ` Björn Töpel
2023-08-23 15:34 ` Randy Dunlap
2023-08-23 15:34   ` Randy Dunlap
2023-08-23 15:44 ` Conor Dooley
2023-08-23 15:44   ` Conor Dooley
2023-08-23 20:10 ` patchwork-bot+linux-riscv [this message]
2023-08-23 20:10   ` patchwork-bot+linux-riscv

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=169282142292.4166.3281543334488200075.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=dfustini@baylibre.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.