From: Mark Brown <broonie@kernel.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: imx: wait_for_completion_timeout(..) for PIO transfers
Date: Tue, 21 Jun 2016 19:51:00 +0100 [thread overview]
Message-ID: <20160621185100.GD28202@sirena.org.uk> (raw)
In-Reply-To: <1466511174-17048-1-git-send-email-christian.gmeiner@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Jun 21, 2016 at 02:12:54PM +0200, Christian Gmeiner wrote:
> [ 240.246067] INFO: task hexdump:1660 blocked for more than 120 seconds.
> [ 240.246089] Not tainted 4.1.17 0000001
> [ 240.246099] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
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: 473 bytes --]
next prev parent reply other threads:[~2016-06-21 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 12:12 [PATCH] spi: imx: wait_for_completion_timeout(..) for PIO transfers Christian Gmeiner
2016-06-21 18:51 ` Mark Brown [this message]
2016-07-01 12:32 ` Christian Gmeiner
2016-07-01 15:01 ` Mark Brown
2016-07-02 13:26 ` Christian Gmeiner
2016-06-21 18:53 ` Applied "spi: imx: wait_for_completion_timeout(..) for PIO transfers" to the spi tree 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=20160621185100.GD28202@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christian.gmeiner@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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;
as well as URLs for NNTP newsgroup(s).