From: Jiri Kosina <jkosina@suse.cz>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Rongrong Cao <rrcao@ambarella.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-2.6.32] sound dapm: fix checking for external widgets bug
Date: Fri, 10 Jul 2009 22:39:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.0907102238150.4232@jikos.suse.cz> (raw)
In-Reply-To: <20090710191925.GA5916@sirena.org.uk>
On Fri, 10 Jul 2009, Mark Brown wrote:
> I also notice that you've CCed trivial@kernel.org. Please don't do that
> except for things that can't possibly cause bugs - a change like this
> doesn't really qualify since while the code clearly looks buggy it's
> always possible that the code is just obscure.
Absolutely.
Nevertheless, when the patch doesn't qualify for trivial queue, and I see
proper maintainers being also involved, I just silently skip the patch,
otherwise I just add proper maintainers to CC and don't apply it to
trivial queue.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2009-07-10 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 6:11 Rongrong Cao
2009-07-10 19:19 ` Mark Brown
2009-07-10 20:39 ` Jiri Kosina [this message]
2009-07-11 5:51 ` 答复: " Rongrong Cao
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=alpine.LNX.2.00.0907102238150.4232@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rrcao@ambarella.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®