All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Argus Lin <argus.lin@mediatek.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>,
	"Tzung-Bi Shih" <tzungbi@google.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Charles Keepax" <ckeepax@opensource.cirrus.com>,
	"ChiPeng Chang (張琦朋)" <chipeng.chang@mediatek.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Dan Murphy" <dmurphy@ti.com>,
	"Shuming Fan" <shumingf@realtek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Shane Chien (簡佑軒)" <Shane.Chien@mediatek.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add mediatek MT6359 accdet driver
Date: Wed, 3 Feb 2021 13:20:51 +0000	[thread overview]
Message-ID: <20210203132051.GC4880@sirena.org.uk> (raw)
In-Reply-To: <1612335462.9202.1.camel@mtkswgap22>

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

On Wed, Feb 03, 2021 at 02:57:42PM +0800, Argus Lin wrote:
> Dear maintainers:
> Can you reply to me if any opinion?
> thanks

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

IIRC I did review this...

[-- 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: Argus Lin <argus.lin@mediatek.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>,
	"Tzung-Bi Shih" <tzungbi@google.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Charles Keepax" <ckeepax@opensource.cirrus.com>,
	"ChiPeng Chang (張琦朋)" <chipeng.chang@mediatek.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Dan Murphy" <dmurphy@ti.com>,
	"Shuming Fan" <shumingf@realtek.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Shane Chien (簡佑軒)" <Shane.Chien@mediatek.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add mediatek MT6359 accdet driver
Date: Wed, 3 Feb 2021 13:20:51 +0000	[thread overview]
Message-ID: <20210203132051.GC4880@sirena.org.uk> (raw)
In-Reply-To: <1612335462.9202.1.camel@mtkswgap22>


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

On Wed, Feb 03, 2021 at 02:57:42PM +0800, Argus Lin wrote:
> Dear maintainers:
> Can you reply to me if any opinion?
> thanks

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

IIRC I did review this...

[-- 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: Argus Lin <argus.lin@mediatek.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>,
	"Tzung-Bi Shih" <tzungbi@google.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Charles Keepax" <ckeepax@opensource.cirrus.com>,
	"ChiPeng Chang (張琦朋)" <chipeng.chang@mediatek.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Dan Murphy" <dmurphy@ti.com>,
	"Shuming Fan" <shumingf@realtek.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Shane Chien (簡佑軒)" <Shane.Chien@mediatek.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add mediatek MT6359 accdet driver
Date: Wed, 3 Feb 2021 13:20:51 +0000	[thread overview]
Message-ID: <20210203132051.GC4880@sirena.org.uk> (raw)
In-Reply-To: <1612335462.9202.1.camel@mtkswgap22>


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

On Wed, Feb 03, 2021 at 02:57:42PM +0800, Argus Lin wrote:
> Dear maintainers:
> Can you reply to me if any opinion?
> thanks

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

IIRC I did review this...

[-- 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: Argus Lin <argus.lin@mediatek.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Charles Keepax" <ckeepax@opensource.cirrus.com>,
	"Arnd Bergmann" <arnd@arndb.de>, "Jack Yu" <jack.yu@realtek.com>,
	"Shuming Fan" <shumingf@realtek.com>,
	"Dan Murphy" <dmurphy@ti.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Jiaxin Yu (俞家鑫)" <Jiaxin.Yu@mediatek.com>,
	"Tzung-Bi Shih" <tzungbi@google.com>,
	"Shane Chien (簡佑軒)" <Shane.Chien@mediatek.com>,
	"ChiPeng Chang (張琦朋)" <chipeng.chang@mediatek.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 0/2] Add mediatek MT6359 accdet driver
Date: Wed, 3 Feb 2021 13:20:51 +0000	[thread overview]
Message-ID: <20210203132051.GC4880@sirena.org.uk> (raw)
In-Reply-To: <1612335462.9202.1.camel@mtkswgap22>

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

On Wed, Feb 03, 2021 at 02:57:42PM +0800, Argus Lin wrote:
> Dear maintainers:
> Can you reply to me if any opinion?
> thanks

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

IIRC I did review this...

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

  reply	other threads:[~2021-02-03 13:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 12:19 [PATCH 0/2] Add mediatek MT6359 accdet driver Argus Lin
2021-01-06 12:19 ` Argus Lin
2021-01-06 12:19 ` [PATCH 1/2] dt-bindings: mediatek: mt6359: add ASoC mt6359 accdet document Argus Lin
2021-01-06 12:19   ` Argus Lin
2021-02-03  6:58   ` Argus Lin
2021-02-03  6:58     ` Argus Lin
2021-02-03  6:58     ` Argus Lin
2021-02-03  6:58     ` Argus Lin
2021-01-06 12:19 ` [PATCH 2/2] ASoC: mediatek: mt6359: add MT6359 accdet driver Argus Lin
2021-01-15 17:07   ` Mark Brown
2021-01-15 17:07     ` Mark Brown
2021-01-15 17:07     ` Mark Brown
2021-01-15 17:07     ` Mark Brown
2021-02-03  6:59   ` Argus Lin
2021-02-03  6:59     ` Argus Lin
2021-02-03  6:57 ` [PATCH 0/2] Add mediatek " Argus Lin
2021-02-03  6:57   ` Argus Lin
2021-02-03  6:57   ` Argus Lin
2021-02-03  6:57   ` Argus Lin
2021-02-03 13:20   ` Mark Brown [this message]
2021-02-03 13:20     ` Mark Brown
2021-02-03 13:20     ` Mark Brown
2021-02-03 13:20     ` 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=20210203132051.GC4880@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Jiaxin.Yu@mediatek.com \
    --cc=Shane.Chien@mediatek.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=argus.lin@mediatek.com \
    --cc=arnd@arndb.de \
    --cc=chipeng.chang@mediatek.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=geert@linux-m68k.org \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=robh+dt@kernel.org \
    --cc=shumingf@realtek.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tiwai@suse.com \
    --cc=tzungbi@google.com \
    --cc=wsd_upstream@mediatek.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.