From: Mark Brown <broonie@kernel.org>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: lgirdwood@gmail.com, krzk@kernel.org, sbkim73@samsung.com,
m.szyprowski@samsung.com, b.zolnierkie@samsung.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic context
Date: Thu, 7 Feb 2019 14:54:06 +0000 [thread overview]
Message-ID: <20190207145406.GD6190@sirena.org.uk> (raw)
In-Reply-To: <21b8ccd7-e379-b4aa-3257-c9644ce3664c@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Thu, Feb 07, 2019 at 03:47:14PM +0100, Sylwester Nawrocki wrote:
> On 2/7/19 15:32, Mark Brown wrote:
> > 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.
> OK, let me trim the backtrace some more and resend.
It's fine, I already applied.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
b.zolnierkie@samsung.com, sbkim73@samsung.com,
lgirdwood@gmail.com, krzk@kernel.org,
linux-kernel@vger.kernel.org, m.szyprowski@samsung.com
Subject: Re: [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic context
Date: Thu, 7 Feb 2019 14:54:06 +0000 [thread overview]
Message-ID: <20190207145406.GD6190@sirena.org.uk> (raw)
In-Reply-To: <21b8ccd7-e379-b4aa-3257-c9644ce3664c@samsung.com>
[-- Attachment #1.1: Type: text/plain, Size: 537 bytes --]
On Thu, Feb 07, 2019 at 03:47:14PM +0100, Sylwester Nawrocki wrote:
> On 2/7/19 15:32, Mark Brown wrote:
> > 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.
> OK, let me trim the backtrace some more and resend.
It's fine, I already applied.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-02-07 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190207142052epcas1p22f1dc03c371674434ff40150cf376b6a@epcas1p2.samsung.com>
2019-02-07 14:20 ` [PATCH] ASoC: samsung: Prevent clk_get_rate() calls in atomic context Sylwester Nawrocki
2019-02-07 14:32 ` Mark Brown
2019-02-07 14:32 ` Mark Brown
2019-02-07 14:47 ` Sylwester Nawrocki
2019-02-07 14:54 ` Mark Brown [this message]
2019-02-07 14:54 ` 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=20190207145406.GD6190@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sbkim73@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.