From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
vamos-dev@i4.informatik.uni-erlangen.de,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Missing config option for SFFSDR_FPGA
Date: Wed, 21 Jul 2010 13:28:53 +0100 [thread overview]
Message-ID: <20100721122853.GA15462@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <86tynthzja.fsf@peer.zerties.org>
On Wed, Jul 21, 2010 at 12:58:33PM +0200, Christian Dietrich wrote:
> As part of the VAMOS[0] research project at the University of
> Erlangen we are looking at multiple integrity errors in linux'
> configuration system.
As I keep saying every time someone reports this problem you really need
to speak to the people responsible for the platform. This is an issue
specific to the relevant board, please contact the maintainers of the
specific system.
If you're going to do this sort of work you need to watch out for
embedded devices - you will need to make sure to contact the people
responsible for the device as well as the subsystem maintainers who
will often have no specific knowledge of the individual systems.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
vamos-dev@i4.informatik.uni-erlangen.de
Subject: Re: Missing config option for SFFSDR_FPGA
Date: Wed, 21 Jul 2010 13:28:53 +0100 [thread overview]
Message-ID: <20100721122853.GA15462@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <86tynthzja.fsf@peer.zerties.org>
On Wed, Jul 21, 2010 at 12:58:33PM +0200, Christian Dietrich wrote:
> As part of the VAMOS[0] research project at the University of
> Erlangen we are looking at multiple integrity errors in linux'
> configuration system.
As I keep saying every time someone reports this problem you really need
to speak to the people responsible for the platform. This is an issue
specific to the relevant board, please contact the maintainers of the
specific system.
If you're going to do this sort of work you need to watch out for
embedded devices - you will need to make sure to contact the people
responsible for the device as well as the subsystem maintainers who
will often have no specific knowledge of the individual systems.
next prev parent reply other threads:[~2010-07-21 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 10:58 Missing config option for SFFSDR_FPGA Christian Dietrich
2010-07-21 10:58 ` Christian Dietrich
2010-07-21 12:28 ` Mark Brown [this message]
2010-07-21 12:28 ` Mark Brown
2010-07-21 12:34 ` Takashi Iwai
2010-07-21 12:34 ` Takashi Iwai
2010-07-21 12:55 ` Mark Brown
2010-07-21 12:55 ` 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=20100721122853.GA15462@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=qy03fugy@stud.informatik.uni-erlangen.de \
--cc=tiwai@suse.de \
--cc=vamos-dev@i4.informatik.uni-erlangen.de \
/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.