public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "John W. Linville" <linville@tuxdriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Raphael Silva <rapphil@gmail•com>
Subject: linux-next: build failure after merge of the wireless-next tree
Date: Wed, 16 Jul 2014 13:28:51 +1000	[thread overview]
Message-ID: <20140716132851.5b974707@canb.auug.org.au> (raw)

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

Hi John,

After merging the wireless-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/staging/rtl8723au/core/rtw_sta_mgt.c: In function 'rtw_free_stainfo23a':
drivers/staging/rtl8723au/core/rtw_sta_mgt.c:254:27: error: expected expression before ';' token
  pstapriv->asoc_sta_count-;
                           ^

Caused by commit 3dd51964026e ("rtl8723au: Corrections in the coding
style") (its always the cleanup patches that cause problems :-))
Please unit test *all* patches.

I have used the wireless-next tree from next-20140715 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-07-16  3:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  3:28 Stephen Rothwell [this message]
2014-07-16 14:09 ` linux-next: build failure after merge of the wireless-next tree John W. Linville
  -- strict thread matches above, loose matches on Subject: below --
2025-01-16  2:08 Stephen Rothwell
2025-01-16  5:49 ` Ping-Ke Shih
2025-01-16 19:30   ` Kalle Valo
2024-10-09  1:04 Stephen Rothwell
2024-10-09  7:04 ` Johannes Berg
2014-09-08  8:42 Stephen Rothwell
2014-09-09 23:28 ` Stephen Rothwell
2014-09-09 23:37   ` David Miller
2014-09-10 17:46     ` John W. Linville
2014-04-23  3:47 Stephen Rothwell
2014-04-23 20:54 ` Bing Zhao
2014-03-06  2:43 Stephen Rothwell
2014-03-06  8:53 ` Arend van Spriel
2014-03-06  2:24 Stephen Rothwell
2014-02-25  2:35 Stephen Rothwell
2014-02-25 19:07 ` John W. Linville
2014-02-25 20:47   ` Stephen Rothwell
2014-03-04 23:16     ` Stephen Rothwell
2014-03-04 23:21       ` Stephen Rothwell
2014-03-04 23:49         ` Greg KH
2014-02-13  2:19 Stephen Rothwell
2014-02-13  2:22 ` Stephen Rothwell
2014-02-13 17:31 ` Paul Gortmaker
2014-02-13 18:22   ` Paul Gortmaker
2014-02-13 18:28     ` Greg KH
2013-07-23  1:32 Stephen Rothwell
2013-07-23  7:24 ` Hauke Mehrtens
2013-04-02  2:34 Stephen Rothwell
2013-04-02  3:07 ` Larry Finger
2013-04-02  3:31   ` Stephen Rothwell
2013-04-02  4:07     ` Larry Finger
2012-04-12  2:24 Stephen Rothwell
2011-12-20  2:18 Stephen Rothwell
2011-12-20  2:42 ` Luis R. Rodriguez
2011-12-20  2:57   ` Stephen Rothwell
2011-12-20  3:24     ` Luis R. Rodriguez
2011-11-22  3:35 Stephen Rothwell
2011-11-22  8:03 ` Stanislaw Gruszka

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=20140716132851.5b974707@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linville@tuxdriver$(echo .)com \
    --cc=rapphil@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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