From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Piotr Hosowicz <piotr@hosowicz.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to submit bug report about linux-next?
Date: Wed, 28 Apr 2010 12:56:22 +0100 [thread overview]
Message-ID: <20100428115622.GA8960@sirena.org.uk> (raw)
In-Reply-To: <4BD81B66.5010809@example.com>
On Wed, Apr 28, 2010 at 01:26:30PM +0200, Piotr Hosowicz wrote:
> Where should I submit a bug report about yesterday's and today's linux-next?
To the relevant mailing lists and maintainers for the affected subsystem
(see MAINTAINERS), or this list if you're not able to identify what's
affected/responsible.
next prev parent reply other threads:[~2010-04-28 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 11:26 Where to submit bug report about linux-next? Piotr Hosowicz
2010-04-28 11:56 ` Mark Brown [this message]
2010-04-28 13:01 ` Piotr Hosowicz
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=20100428115622.GA8960@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.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.