Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Neil Brown <neilb@suse.de>
Cc: linux-next@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: linux-next: manual merge of the md tree
Date: Wed, 15 Oct 2008 19:41:45 +1100	[thread overview]
Message-ID: <20081015194145.f11c34e9.sfr@canb.auug.org.au> (raw)

Hi Neil,

Today's linux-next merge of the md tree got a conflict in drivers/md/md.c
between commit d8ade4ef35e2ae74b4d4b012eacd16ac1c34ad50 ("remove
CONFIG_KMOD from drivers") from the rr tree and commit
6caa3b0bbdb474647f6bdd8a958ffc46f78d8d58 ("md: Remove unnecessary
#includes, #defines, and function declarations") from the md tree.

Overlapping removals. I fixed it up (see below) and can carry the fix.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc drivers/md/md.c
index 3323d76,8a34fc9..0000000
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@@ -41,17 -38,14 +38,15 @@@
  #include <linux/sysctl.h>
  #include <linux/buffer_head.h> /* for invalidate_bdev */
  #include <linux/poll.h>
- #include <linux/mutex.h>
  #include <linux/ctype.h>
- #include <linux/freezer.h>
- #include <linux/init.h>
- #include <linux/file.h>
 +#include <linux/kmod.h>
- 
- #include <asm/unaligned.h>
+ #include <linux/hdreg.h>
+ #include <linux/proc_fs.h>
+ #include <linux/random.h>
+ #include <linux/reboot.h>
+ #include <linux/file.h>
  
  #define MAJOR_NR MD_MAJOR
- #define MD_DRIVER
  
  /* 63 partitions with the alternate major number (mdp) */
  #define MdpMinorShift 6

             reply	other threads:[~2008-10-15  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  8:41 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15  8:34 linux-next: manual merge of the md tree Stephen Rothwell
2008-10-15 10:52 ` Neil Brown
2008-10-16  6:07   ` Stephen Rothwell
2008-10-16  6:13     ` 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=20081015194145.f11c34e9.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=johannes@sipsolutions.net \
    --cc=linux-next@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rusty@rustcorp.com.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