From: Mark Brown <broonie@kernel.org>
To: "wuxu.wu" <wuxu.wu@huawei.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
hushiyuan@huawei.com
Subject: Re: [PATCH] spi: spi-dw: Add lock protect dw_spi rx/tx to prevent concurrent calls
Date: Thu, 19 Dec 2019 16:41:25 +0000 [thread overview]
Message-ID: <20191219164125.GG5047@sirena.org.uk> (raw)
In-Reply-To: <1576767380-12947-1-git-send-email-wuxu.wu@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Thu, Dec 19, 2019 at 10:56:20PM +0800, wuxu.wu wrote:
> [ 1025.321405] default_idle_call+0x30/0x4c
> [ 1025.321415] do_idle+0x22c/0x300
> [ 1025.321417] cpu_startup_entry+0x28/0x30
> [ 1025.321426] secondary_start_kernel+0x17c/0x1c8
> ---
> drivers/spi/spi-dw.c | 17 ++++++++++++++---
> drivers/spi/spi-dw.h | 1 +
You haven't provided a signoff so I can't do anything with this, see
submitting-patches.rst for details on what this is and why it is
essential. That also has some other information on formatting
submissions.
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative then it's
usually better to pull out the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2019-12-19 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1576767380-12947-1-git-send-email-wuxu.wu@huawei.com>
2019-12-19 16:41 ` Mark Brown [this message]
[not found] <1576900099-40754-1-git-send-email-wuxu.wu@huawei.com>
2019-12-27 0:50 ` Mark Brown
[not found] <1577418669-34821-1-git-send-email-wuxu.wu@huawei.com>
2019-12-31 0:29 ` Mark Brown
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=20191219164125.GG5047@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hushiyuan@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=wuxu.wu@huawei.com \
/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®