All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <greg@kroah.com>, Vinod Koul <vinod.koul@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Staging clear up
Date: Wed, 9 Nov 2011 23:11:24 +0000	[thread overview]
Message-ID: <20111109231124.GC17769@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111109230558.2fb94c0b@lxorguk.ukuu.org.uk>

On Wed, Nov 09, 2011 at 11:05:58PM +0000, Alan Cox wrote:

> Yes - then it doesn't compile. The codec is calling functions defined in
> that header. I don't think you need much of it but both bits of that
> driver are using some of the stuff.

Oh, actually the mainline CODEC driver doesn't have any such staging
references in it at all.  I don't know what tree you're patching
against?

  reply	other threads:[~2011-11-09 23:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 21:16 Staging clear up Alan Cox
2011-11-08 21:48 ` Greg KH
2011-11-08 23:51   ` Alan Cox
2011-11-09  0:05     ` Greg KH
2011-11-09 12:13 ` Mark Brown
2011-11-09 16:00   ` Vinod Koul
2011-11-09 16:42     ` Mark Brown
2011-11-09 16:47       ` Vinod Koul
2011-11-09 16:53         ` Mark Brown
2011-11-09 17:03           ` Vinod Koul
2011-11-09 17:08             ` Mark Brown
2011-11-09 17:12               ` Vinod Koul
2011-11-10  9:49                 ` Dimitris Papastamos
2011-11-09 16:55       ` Greg KH
2011-11-09 16:58         ` Mark Brown
2011-11-09 17:30           ` Alan Cox
2011-11-09 22:59             ` Mark Brown
2011-11-09 23:03               ` Alan Cox
2011-11-09 23:03                 ` Mark Brown
2011-11-09 23:05                   ` Alan Cox
2011-11-09 23:11                     ` Mark Brown [this message]
2011-11-09 23:25                       ` Alan Cox
2011-11-10  2:52                         ` Vinod Koul
2011-11-10  8:54                           ` Alan Cox
2011-11-27  1:30 ` Greg KH

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=20111109231124.GC17769@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@linux.intel.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.