public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	Jaroslav Kysela <perex@perex.cz>,
	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 14:34:25 +0200	[thread overview]
Message-ID: <s5htynt2eum.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100721122853.GA15462@rakim.wolfsonmicro.main>

At Wed, 21 Jul 2010 13:28:53 +0100,
Mark Brown wrote:
> 
> 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.

The problem is that the drivers for embedded platforms are often out
of sync.  davinci is one of such platforms.  So, as Mark suggested,
it'd be better to talk with guys responsible for such a system
beforehand.

Of course, as upstream, we can clean up things here.  But, I'd like to
see this clean-up rather from the platform side.  In that way, it can
be synchronized better.


thanks,

Takashi

  reply	other threads:[~2010-07-21 12:34 UTC|newest]

Thread overview: 4+ 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 12:28 ` Mark Brown
2010-07-21 12:34   ` Takashi Iwai [this message]
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=s5htynt2eum.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=perex@perex.cz \
    --cc=qy03fugy@stud.informatik.uni-erlangen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox