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,
	Paul Gortmaker <paul.gortmaker@windriver•com>
Subject: linux-next: manual merge of the wireless tree with Linus' tree
Date: Wed, 4 Jan 2012 12:40:20 +1100	[thread overview]
Message-ID: <20120104124020.5b481be704bd0040219ee0e0@canb.auug.org.au> (raw)

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

Hi John,

Today's linux-next merge of the wireless tree got a conflict in
drivers/net/wireless/rtlwifi/rtl8192cu/sw.c between commit 9d9779e723a5
("drivers/net: Add module.h to drivers who were implicitly using it")
from the  tree and commit e97173c985c0 ("rtl8192cu: Fix WARNING on
suspend/resume") from the wireless tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
index c244f2f,a48bea6..0000000
--- a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
+++ b/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
@@@ -42,7 -42,8 +42,9 @@@
  #include "led.h"
  #include "hw.h"
  #include <linux/vmalloc.h>
 +#include <linux/module.h>
+ #include <linux/atomic.h>
+ #include <linux/types.h>
  
  MODULE_AUTHOR("Georgia		<georgia@realtek•com>");
  MODULE_AUTHOR("Ziv Huang	<ziv_huang@realtek•com>");

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

             reply	other threads:[~2012-01-04  1:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  1:40 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-14  0:19 linux-next: manual merge of the wireless tree with Linus' tree Stephen Rothwell
2011-09-20  3:28 Stephen Rothwell
2011-09-20 12:55 ` John W. Linville
2011-09-20  3:22 Stephen Rothwell
2011-09-19  5:14 Stephen Rothwell
2011-09-19  5:28 ` Luciano Coelho
2011-09-15  3:14 Stephen Rothwell
2011-09-15  7:17 ` Helmut Schaa
2011-09-15  3:14 Stephen Rothwell
2011-08-30  3:46 Stephen Rothwell
2011-05-12  1:42 Stephen Rothwell
2011-05-11  1:52 Stephen Rothwell
2011-04-27  1:00 Stephen Rothwell
2011-04-13  2:30 Stephen Rothwell
2011-04-08  4:10 Stephen Rothwell
2011-04-08  5:11 ` Jussi Kivilinna
2011-04-08  4:10 Stephen Rothwell
2010-09-21  2:20 Stephen Rothwell
2010-09-21  2:09 Stephen Rothwell
2010-09-21  6:53 ` Ohad Ben-Cohen
2010-09-21  8:57   ` Ohad Ben-Cohen
2010-09-21 15:08 ` John W. Linville
2010-08-17  1:52 Stephen Rothwell
2010-08-17  2:59 ` Rusty Russell
2010-08-17  3:07   ` Stephen Rothwell
2010-06-15  2:00 Stephen Rothwell
2010-06-15 14:42 ` John W. Linville
2010-05-10  1:27 Stephen Rothwell
2010-04-27  1:28 Stephen Rothwell
2010-01-06  2:29 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=20120104124020.5b481be704bd0040219ee0e0@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=paul.gortmaker@windriver$(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