All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after final merge (sound tree)
Date: Wed, 17 Feb 2010 10:01:33 +0000	[thread overview]
Message-ID: <20100217100132.GA19077@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20100217171923.ea505d0f.sfr@canb.auug.org.au>

On Wed, Feb 17, 2010 at 05:19:23PM +1100, Stephen Rothwell wrote:

> After merging, today's linux-next build (powerpc allyesconfig) produced
> this warning:

Oh, feh.  My working copy has this warning fixed but apparently that
didn't make it over.  I'll push a refresh out later today.

One of these days mainline will actually build and do something useful
with audio on a system I can use for normal development.  :/

      reply	other threads:[~2010-02-17 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  6:19 linux-next: build warning after final merge (sound tree) Stephen Rothwell
2010-02-17 10:01 ` Mark Brown [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=20100217100132.GA19077@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.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.