From: Mark Brown <broonie@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: lgirdwood@gmail.com, khilman@baylibre.com, tiwai@suse.com,
perex@perex.cz, linux-amlogic@lists.infradead.org,
linux-kernel@vger.kernel.org, jbrunet@baylibre.com
Subject: Re: [PATCH] sound/soc/meson: fix irq leak in error path
Date: Mon, 9 Mar 2020 16:59:18 +0000 [thread overview]
Message-ID: <20200309165918.GI4101@sirena.org.uk> (raw)
In-Reply-To: <20200309162912.GA21498@amd>
[-- Attachment #1.1: Type: text/plain, Size: 443 bytes --]
On Mon, Mar 09, 2020 at 05:29:12PM +0100, Pavel Machek wrote:
> Irq seems to be leaked in error path. Fix that.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: jbrunet@baylibre.com, lgirdwood@gmail.com, perex@perex.cz,
tiwai@suse.com, khilman@baylibre.com,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound/soc/meson: fix irq leak in error path
Date: Mon, 9 Mar 2020 16:59:18 +0000 [thread overview]
Message-ID: <20200309165918.GI4101@sirena.org.uk> (raw)
In-Reply-To: <20200309162912.GA21498@amd>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Mon, Mar 09, 2020 at 05:29:12PM +0100, Pavel Machek wrote:
> Irq seems to be leaked in error path. Fix that.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-09 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 16:29 [PATCH] sound/soc/meson: fix irq leak in error path Pavel Machek
2020-03-09 16:29 ` Pavel Machek
2020-03-09 16:46 ` Jerome Brunet
2020-03-09 16:46 ` Jerome Brunet
2020-03-09 16:59 ` Mark Brown [this message]
2020-03-09 16:59 ` 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=20200309165918.GI4101@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=perex@perex.cz \
--cc=tiwai@suse.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.