All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: James Liao <jamesjj.liao@mediatek.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Jiasheng Jiang <jiasheng@iscas.ac.cn>,
	linux-kernel@vger.kernel.org,
	Daniel Golle <daniel@makrotopia.org>,
	linux-mediatek@lists.infradead.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Revert "ASoC: mediatek: Check for error clk pointer"
Date: Mon, 7 Feb 2022 13:17:23 +0000	[thread overview]
Message-ID: <YgEb42YZI1iKwqiS@sirena.org.uk> (raw)
In-Reply-To: <20220205014755.699603-1-linux@roeck-us.net>


[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

On Fri, Feb 04, 2022 at 05:47:55PM -0800, Guenter Roeck wrote:
> This reverts commit 9de2b9286a6dd16966959b3cb34fc2ddfd39213e.

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.

Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	Jiasheng Jiang <jiasheng@iscas.ac.cn>,
	James Liao <jamesjj.liao@mediatek.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Frank Wunderlich <frank-w@public-files.de>,
	Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH] Revert "ASoC: mediatek: Check for error clk pointer"
Date: Mon, 7 Feb 2022 13:17:23 +0000	[thread overview]
Message-ID: <YgEb42YZI1iKwqiS@sirena.org.uk> (raw)
In-Reply-To: <20220205014755.699603-1-linux@roeck-us.net>


[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

On Fri, Feb 04, 2022 at 05:47:55PM -0800, Guenter Roeck wrote:
> This reverts commit 9de2b9286a6dd16966959b3cb34fc2ddfd39213e.

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.

Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	Jiasheng Jiang <jiasheng@iscas.ac.cn>,
	James Liao <jamesjj.liao@mediatek.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Frank Wunderlich <frank-w@public-files.de>,
	Daniel Golle <daniel@makrotopia.org>
Subject: Re: [PATCH] Revert "ASoC: mediatek: Check for error clk pointer"
Date: Mon, 7 Feb 2022 13:17:23 +0000	[thread overview]
Message-ID: <YgEb42YZI1iKwqiS@sirena.org.uk> (raw)
In-Reply-To: <20220205014755.699603-1-linux@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Fri, Feb 04, 2022 at 05:47:55PM -0800, Guenter Roeck wrote:
> This reverts commit 9de2b9286a6dd16966959b3cb34fc2ddfd39213e.

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.

Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-02-07 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05  1:47 [PATCH] Revert "ASoC: mediatek: Check for error clk pointer" Guenter Roeck
2022-02-05  1:47 ` Guenter Roeck
2022-02-05  1:47 ` Guenter Roeck
2022-02-07 13:17 ` Mark Brown [this message]
2022-02-07 13:17   ` Mark Brown
2022-02-07 13:17   ` 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=YgEb42YZI1iKwqiS@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=daniel@makrotopia.org \
    --cc=jamesjj.liao@mediatek.com \
    --cc=jiasheng@iscas.ac.cn \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@gmail.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.