From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Neil Brown <neilb@suse.de>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the md-current tree with Linus' tree
Date: Mon, 14 Dec 2009 11:27:26 +0100 [thread overview]
Message-ID: <200912141127.27019.arnd@arndb.de> (raw)
In-Reply-To: <20091214102428.f50557a0.sfr@canb.auug.org.au>
On Monday 14 December 2009, Stephen Rothwell wrote:
> index 278020d,ad485ba..0000000
> --- a/fs/compat_ioctl.c
> +++ b/fs/compat_ioctl.c
> @@@ -979,29 -1912,22 +979,11 @@@ COMPATIBLE_IOCTL(FIGETBSZ
> /* 'X' - originally XFS but some now in the VFS */
> COMPATIBLE_IOCTL(FIFREEZE)
> COMPATIBLE_IOCTL(FITHAW)
> - /* RAID */
> - COMPATIBLE_IOCTL(RAID_VERSION)
> - COMPATIBLE_IOCTL(GET_ARRAY_INFO)
> - COMPATIBLE_IOCTL(GET_DISK_INFO)
> - COMPATIBLE_IOCTL(PRINT_RAID_DEBUG)
> - COMPATIBLE_IOCTL(RAID_AUTORUN)
> - COMPATIBLE_IOCTL(CLEAR_ARRAY)
> - COMPATIBLE_IOCTL(ADD_NEW_DISK)
> - COMPATIBLE_IOCTL(SET_ARRAY_INFO)
> - COMPATIBLE_IOCTL(SET_DISK_INFO)
> - COMPATIBLE_IOCTL(WRITE_RAID_INFO)
> - COMPATIBLE_IOCTL(UNPROTECT_ARRAY)
> - COMPATIBLE_IOCTL(PROTECT_ARRAY)
> - COMPATIBLE_IOCTL(RUN_ARRAY)
> - COMPATIBLE_IOCTL(STOP_ARRAY)
> - COMPATIBLE_IOCTL(STOP_ARRAY_RO)
> - COMPATIBLE_IOCTL(RESTART_ARRAY_RW)
> - COMPATIBLE_IOCTL(GET_BITMAP_FILE)
> -/* Big K */
> -COMPATIBLE_IOCTL(PIO_FONT)
> -COMPATIBLE_IOCTL(GIO_FONT)
> -COMPATIBLE_IOCTL(PIO_CMAP)
> -COMPATIBLE_IOCTL(GIO_CMAP)
> -ULONG_IOCTL(KDSIGACCEPT)
> COMPATIBLE_IOCTL(KDGETKEYCODE)
> COMPATIBLE_IOCTL(KDSETKEYCODE)
> -ULONG_IOCTL(KIOCSOUND)
> -ULONG_IOCTL(KDMKTONE)
> COMPATIBLE_IOCTL(KDGKBTYPE)
> -ULONG_IOCTL(KDSETMODE)
> COMPATIBLE_IOCTL(KDGETMODE)
> -ULONG_IOCTL(KDSKBMODE)
> COMPATIBLE_IOCTL(KDGKBMODE)
> -ULONG_IOCTL(KDSKBMETA)
> COMPATIBLE_IOCTL(KDGKBMETA)
> COMPATIBLE_IOCTL(KDGKBENT)
> COMPATIBLE_IOCTL(KDSKBENT)
This merge is incomplete, because the patch that I made for Neil
removes the handling for HOT_REMOVE_DISK, HOT_ADD_DISK,
SET_DISK_FAULTY and SET_BITMAP_FILE from fs/compat_ioctl.c
along with the others above, while my other patch that Linus
merged moves them into the switch statement in do_ioctl_trans.
Neil, still have a tree where I track patches to fs/compat_ioctl.c
that have not yet been merged. If you just keep the half in your
own files and drop the ones in fs/compat_ioctl.c, I'll submit that
next time. You can also adapt the patch again to the new contents
and remove the four above to save me that work.
I didn't want to remove them from fs/compat_ioctl.c before they
got added to md.c, in order to keep bisection correct.
Arnd
next prev parent reply other threads:[~2009-12-14 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 23:24 linux-next: manual merge of the md-current tree with Linus' tree Stephen Rothwell
2009-12-14 10:27 ` Arnd Bergmann [this message]
2009-12-15 3:05 ` Neil Brown
2009-12-15 9:57 ` Arnd Bergmann
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=200912141127.27019.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neilb@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.