From: Stefan Agner <stefan@agner.ch>
To: Mark Brown <broonie@kernel.org>
Cc: timur@tabi.org, Xiubo.Lee@gmail.com, fabio.estevam@nxp.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Nicolin Chen <nicoleotsuka@gmail.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: fsl_asrc: protect macro argument
Date: Wed, 06 Dec 2017 16:03:24 +0100 [thread overview]
Message-ID: <a79ecfeb4b74ba18fe839d53e0f874f8@agner.ch> (raw)
In-Reply-To: <20171206143950.irihxu25xg7jut4e@sirena.org.uk>
On 2017-12-06 15:39, Mark Brown wrote:
> On Wed, Dec 06, 2017 at 03:25:37PM +0100, Stefan Agner wrote:
>> On 2017-12-06 15:11, Mark Brown wrote:
>
[...]
>> I did not meant to bug people, just wanted to make sure the patch does
>> not falls through the cracks... After all, patch as well as the Ack
>> already more than 3 months old....
>
> You need to send patches to the relevant maintainers as covered in
> SubmittingPatches, if you don't send us patches we won't have them and
> can't apply them.
Yeah this is where it gets a bit fuzzy around the affected file, there
are maintainers mentioned in the MAINTAINER file but I just realized
today that it was typically you which merged patches for the file.
Will resend the patch and add you as recipient.
--
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Agner <stefan@agner.ch>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Xiubo.Lee@gmail.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
timur@tabi.org, Nicolin Chen <nicoleotsuka@gmail.com>,
fabio.estevam@nxp.com
Subject: Re: [PATCH] ASoC: fsl_asrc: protect macro argument
Date: Wed, 06 Dec 2017 16:03:24 +0100 [thread overview]
Message-ID: <a79ecfeb4b74ba18fe839d53e0f874f8@agner.ch> (raw)
In-Reply-To: <20171206143950.irihxu25xg7jut4e@sirena.org.uk>
On 2017-12-06 15:39, Mark Brown wrote:
> On Wed, Dec 06, 2017 at 03:25:37PM +0100, Stefan Agner wrote:
>> On 2017-12-06 15:11, Mark Brown wrote:
>
[...]
>> I did not meant to bug people, just wanted to make sure the patch does
>> not falls through the cracks... After all, patch as well as the Ack
>> already more than 3 months old....
>
> You need to send patches to the relevant maintainers as covered in
> SubmittingPatches, if you don't send us patches we won't have them and
> can't apply them.
Yeah this is where it gets a bit fuzzy around the affected file, there
are maintainers mentioned in the MAINTAINER file but I just realized
today that it was typically you which merged patches for the file.
Will resend the patch and add you as recipient.
--
Stefan
next prev parent reply other threads:[~2017-12-06 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 6:36 [PATCH] ASoC: fsl_asrc: protect macro argument Stefan Agner
2017-08-07 7:08 ` Nicolin Chen
2017-12-06 13:53 ` Stefan Agner
2017-12-06 14:11 ` Mark Brown
2017-12-06 14:25 ` Stefan Agner
2017-12-06 14:39 ` Mark Brown
2017-12-06 14:39 ` Mark Brown
2017-12-06 15:03 ` Stefan Agner [this message]
2017-12-06 15:03 ` Stefan Agner
2017-12-06 15:29 ` Applied "ASoC: fsl_asrc: protect macro argument" to the asoc tree Mark Brown
2017-12-06 15:29 ` 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=a79ecfeb4b74ba18fe839d53e0f874f8@agner.ch \
--to=stefan@agner.ch \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=timur@tabi.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 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.