From: Piotr Hosowicz <piotr@hosowicz.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to submit bug report about linux-next?
Date: Wed, 28 Apr 2010 15:01:39 +0200 [thread overview]
Message-ID: <4BD831B3.40907@example.com> (raw)
In-Reply-To: <20100428115622.GA8960@sirena.org.uk>
On 28.04.2010 13:56, Mark Brown wrote:
> 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.
I dont know which one is relevant and dont see apropriate person
regarding SMP. This is probably the problem. I'll send here in a moment.
Rergards,
Piotr Hosowicz
--
TV: "Jeszcze trzy ruchy i Otylia będzie szczęśliwa."
NP: Mark Knopfler - Border Reiver
NB: 2.6.34-rc5-git8
prev parent reply other threads:[~2010-04-28 13:01 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
2010-04-28 13:01 ` Piotr Hosowicz [this message]
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=4BD831B3.40907@example.com \
--to=piotr@hosowicz.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox