From: Mark Brown <broonie@kernel.org> To: Brian Norris <briannorris@chromium.org> Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Takashi Iwai <tiwai@suse.com>, alsa-devel@alsa-project.org Subject: Re: [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Date: Tue, 14 Mar 2017 14:36:54 +0100 [thread overview] Message-ID: <20170314133654.w5neqkkaennht7lm@sirena.org.uk> (raw) In-Reply-To: <20170313215256.GD4586@google.com> [-- Attachment #1: Type: text/plain, Size: 907 bytes --] On Mon, Mar 13, 2017 at 02:52:56PM -0700, Brian Norris wrote: > Sure, I can understand frustration with essentially contentless "bug > reports." And I got frustrated by a seemingly pat response that was > (IMO) a bit mistargeted. It *is* a pat response, it's one of the things I find I have to send often enough that I've got a canned response for it - I find that if I don't do things like that then after a while what gets sent becomes so brief that unless you're really familiar with what's being said it can be hard to understand the feedback. It's tricky though because as you say it's fairly obvious it's a form letter. > BTW, I don't see the patch applied anywhere (and I have no reply - > either manual or automated/patchwork - other than the above quote to say > it was). 20170309102819.bx5paxtffvmvmuov@sirena.org.uk, fix/core Didn't seem to have made -next today, guess it'll hit tomorrow. [-- 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: Brian Norris <briannorris@chromium.org> Cc: alsa-devel@alsa-project.org, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com> Subject: Re: [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Date: Tue, 14 Mar 2017 14:36:54 +0100 [thread overview] Message-ID: <20170314133654.w5neqkkaennht7lm@sirena.org.uk> (raw) In-Reply-To: <20170313215256.GD4586@google.com> [-- Attachment #1.1: Type: text/plain, Size: 907 bytes --] On Mon, Mar 13, 2017 at 02:52:56PM -0700, Brian Norris wrote: > Sure, I can understand frustration with essentially contentless "bug > reports." And I got frustrated by a seemingly pat response that was > (IMO) a bit mistargeted. It *is* a pat response, it's one of the things I find I have to send often enough that I've got a canned response for it - I find that if I don't do things like that then after a while what gets sent becomes so brief that unless you're really familiar with what's being said it can be hard to understand the feedback. It's tricky though because as you say it's fairly obvious it's a form letter. > BTW, I don't see the patch applied anywhere (and I have no reply - > either manual or automated/patchwork - other than the above quote to say > it was). 20170309102819.bx5paxtffvmvmuov@sirena.org.uk, fix/core Didn't seem to have made -next today, guess it'll hit tomorrow. [-- 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:[~2017-03-14 13:37 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-08 23:18 [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-08 23:18 ` Brian Norris 2017-03-09 0:17 ` Kuninori Morimoto 2017-03-09 0:17 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Kuninori Morimoto 2017-03-09 0:21 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-09 0:53 ` Kuninori Morimoto 2017-03-09 0:53 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Kuninori Morimoto 2017-03-11 0:39 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-13 3:46 ` Kuninori Morimoto 2017-03-13 3:46 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Kuninori Morimoto 2017-03-13 21:41 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-14 1:07 ` Kuninori Morimoto 2017-03-14 1:07 ` Kuninori Morimoto 2017-03-09 11:09 ` Mark Brown 2017-03-09 11:09 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Mark Brown 2017-03-11 0:24 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-13 12:50 ` Mark Brown 2017-03-13 12:50 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} Mark Brown 2017-03-13 21:52 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new,free} Brian Norris 2017-03-14 13:36 ` Mark Brown [this message] 2017-03-14 13:36 ` [PATCH for-4.11] ASoC: don't dereference NULL pcm_{new, free} 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=20170314133654.w5neqkkaennht7lm@sirena.org.uk \ --to=broonie@kernel.org \ --cc=alsa-devel@alsa-project.org \ --cc=briannorris@chromium.org \ --cc=kuninori.morimoto.gx@renesas.com \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.