linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 12
Date: Thu, 12 Mar 2015 10:36:40 +0000	[thread overview]
Message-ID: <20150312103640.GL28806@sirena.org.uk> (raw)
In-Reply-To: <20150312212631.1df37d57@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

On Thu, Mar 12, 2015 at 09:26:31PM +1100, Stephen Rothwell wrote:

> This is the error I have been getting for the past couple of days:

> sound/soc/codecs/rt5670.c: In function 'is_sys_clk_from_pll':
> sound/soc/codecs/rt5670.c:702:38: error: 'struct snd_soc_dapm_widget' has no member named 'codec'
>   struct snd_soc_codec *codec = source->codec;
>                                       ^

> The line number has changed (from 519 to 702) but the function name and
> text is the same.

> There was another error (the bad merge resolution) that is gone today.

OK, I'd only see the bad merge resolution.

> Bard Liao pointed at this patch today:
> http://mailman.alsa-project.org/pipermail/alsa-devel/2015-January/086618.html
> which is not in the sound-asoc tree I fetched today (top commit
> ddb1fb8f0089).  I just did another fetch and it didn't change.

It's there now.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-03-12 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  5:53 linux-next: Tree for Mar 12 Stephen Rothwell
2015-03-12  9:58 ` Mark Brown
2015-03-12 10:26   ` Stephen Rothwell
2015-03-12 10:36     ` Mark Brown [this message]
2015-03-12 11:24       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-03-12  4:40 Stephen Rothwell
2021-03-12  5:20 Stephen Rothwell
2020-03-12 10:04 Stephen Rothwell
2013-03-12  4:52 Stephen Rothwell

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=20150312103640.GL28806@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).