From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-rt-users@vger.kernel.org, linux-serial@vger.kernel.org,
linux-sh@vger.kernel.org, gregkh@linuxfoundation.org,
Daniel Wagner <daniel.wagner@siemens.com>
Subject: Re: [PATCH v2] serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version
Date: Tue, 8 May 2018 09:18:44 +0200 [thread overview]
Message-ID: <d37e074d-5e8c-84e8-5833-7ff595e6348c@monom.org> (raw)
In-Reply-To: <20180507125146.75crpaj2scav7mql@linutronix.de>
Hi Sebastian,
On 05/07/2018 02:51 PM, Sebastian Andrzej Siewior wrote:
> On 2018-05-04 18:30:41 [+0200], Daniel Wagner wrote:
>> --- a/drivers/tty/serial/sh-sci.c
>> +++ b/drivers/tty/serial/sh-sci.c
>> @@ -2890,16 +2890,16 @@ static void serial_console_write(struct console *co, const char *s,
>> unsigned long flags;
>> int locked = 1;
>>
>> - local_irq_save(flags);
>> #if defined(SUPPORT_SYSRQ)
>> - if (port->sysrq)
>> + if (port->sysrq) {
>> locked = 0;
>> - else
>> + local_irq_save(flags);
>
> how is this helping? You should see a splat after a sysrq request.
You are right, I didn't really think this through.
Should 'echo t > /proc/sysrq' trigger the splat? At least I was so naive
that think it would be enough.
Thanks,
Daniel
next prev parent reply other threads:[~2018-05-08 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 16:30 Daniel Wagner
2018-05-07 7:14 ` Geert Uytterhoeven
2018-05-07 12:51 ` Sebastian Andrzej Siewior
2018-05-08 7:18 ` Daniel Wagner [this message]
2018-05-08 7:40 ` Sebastian Andrzej Siewior
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=d37e074d-5e8c-84e8-5833-7ff595e6348c@monom.org \
--to=wagi@monom.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@siemens.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@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
all inboxes | Powered by JetHome®