From: Alexey Dobriyan <adobriyan@gmail.com>
To: Christian Brauner <christian@brauner.io>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 12/17] signal: make unhandled_signal() return bool
Date: Sat, 2 Jun 2018 15:02:38 +0300 [thread overview]
Message-ID: <20180602120238.GA11282@avx2> (raw)
> -int unhandled_signal(struct task_struct *tsk, int sig)
> +bool unhandled_signal(struct task_struct *tsk, int sig)
This most likely makes code generation worse on embedded arhcs
which will '& 0xFF" internally.
next reply other threads:[~2018-06-02 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 12:02 Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-02 10:36 [PATCH v3 00/17] signal: refactor some functions Christian Brauner
2018-06-02 10:36 ` [PATCH v3 12/17] signal: make unhandled_signal() return bool Christian Brauner
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=20180602120238.GA11282@avx2 \
--to=adobriyan@gmail.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.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