From: Stafford Horne <shorne@gmail.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: openrisc@lists.librecores.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] openrisc: signal: remove unused DEBUG_SIG macro
Date: Thu, 21 Oct 2021 05:38:53 +0900 [thread overview]
Message-ID: <YXB+XVb/mBlI5fWo@antec> (raw)
In-Reply-To: <20211020121637.6629-1-kda@linux-powerpc.org>
On Wed, Oct 20, 2021 at 03:16:37PM +0300, Denis Kirjanov wrote:
> Signed-off-by: Denis Kirjanov <kda@linux-powerpc.org>
> ---
> arch/openrisc/kernel/signal.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/openrisc/kernel/signal.c b/arch/openrisc/kernel/signal.c
> index 1ebcff271096..99516c9191c7 100644
> --- a/arch/openrisc/kernel/signal.c
> +++ b/arch/openrisc/kernel/signal.c
> @@ -28,8 +28,6 @@
> #include <asm/ucontext.h>
> #include <linux/uaccess.h>
>
> -#define DEBUG_SIG 0
> -
> struct rt_sigframe {
> struct siginfo info;
> struct ucontext uc;
This looks ok to me. I will queue it.
Thanks.
-Stafford
prev parent reply other threads:[~2021-10-20 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 12:16 [PATCH] openrisc: signal: remove unused DEBUG_SIG macro Denis Kirjanov
2021-10-20 20:38 ` Stafford Horne [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=YXB+XVb/mBlI5fWo@antec \
--to=shorne@gmail.com \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox