From: Takashi Iwai <tiwai@suse.de>
To: Macpaul Lin <macpaul.lin@mediatek.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Takashi Iwai <tiwai@suse.de>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound-current tree
Date: Fri, 05 Jun 2020 08:39:51 +0200 [thread overview]
Message-ID: <s5ho8py818o.wl-tiwai@suse.de> (raw)
In-Reply-To: <1591323509.7223.2.camel@mtkswgap22>
On Fri, 05 Jun 2020 04:18:29 +0200,
Macpaul Lin wrote:
>
> On Fri, 2020-06-05 at 08:43 +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the sound-current tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > /home/sfr/next/next/sound/usb/card.c: In function 'snd_usb_autoresume':
> > /home/sfr/next/next/sound/usb/card.c:841:29: error: expected ';' before ')' token
> > 841 | atomic_dec(&chip->active))
> > | ^
> > | ;
> >
> > Caused by commit
> >
> > 3398e5c7b038 ("ALSA: usb-audio: Manage auto-pm of all bundled interfaces")
> >
> > I have reverted that commit for today.
> >
>
> Sorry I've tested its function by "patch back" to older kernel version
> 4.14.
> After checking the latest patch again, there is indeed a typo here.
Sorry for the mess, somehow a wrong version was pushed and merged.
I also tested but overlooked it...
Will scratch and resubmit the corrected one.
Takashi
next prev parent reply other threads:[~2020-06-05 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 22:43 linux-next: build failure after merge of the sound-current tree Stephen Rothwell
2020-06-05 2:18 ` Macpaul Lin
2020-06-05 6:39 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-09 23:00 Stephen Rothwell
2021-11-10 6:20 ` Takashi Iwai
2024-03-12 21:51 Stephen Rothwell
2024-03-13 8:01 ` Takashi Iwai
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=s5ho8py818o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macpaul.lin@mediatek.com \
--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