From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Subject: linux-next: build failure after merge of the sound-current tree
Date: Tue, 13 Jun 2017 07:29:12 +0200 [thread overview]
Message-ID: <s5htw3kxxp3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170613094945.06fbd573@canb.auug.org.au>
On Tue, 13 Jun 2017 01:49:45 +0200,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> After merging the sound-current tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/synth/emux/emux.c: In function 'snd_emux_new':
> sound/synth/emux/emux.c:51:5: error: 'struct snd_emux' has no member named 'oss_synth'
My bad, some devel branch sneaked in to for-linus branch
accidentally. Now it's backed out.
Something went wrong in my script recently. I need to tune it again.
Sorry for inconvenience.
Takashi
next prev parent reply other threads:[~2017-06-13 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 23:49 Subject: linux-next: build failure after merge of the sound-current tree Stephen Rothwell
2017-06-13 5:29 ` Takashi Iwai [this message]
2017-06-13 5:59 ` 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=s5htw3kxxp3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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