From: John Kacur <jkacur@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: John Kacur <jkacur@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jan Blunck <jblunck@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes
Date: Tue, 27 Apr 2010 14:19:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1004271359180.3318@localhost> (raw)
In-Reply-To: <201004271331.58130.arnd@arndb.de>
On Tue, 27 Apr 2010, Arnd Bergmann wrote:
> On Tuesday 27 April 2010, John Kacur wrote:
> > These are bkl pushdowns from Arnd that conflicted with
> > Linus's "Preparation for BKL'ed ioctl removal patch". I fixed-up the merge
> > conflicts. In addition - during allyesconfig compile testing on x86_64 I found
> > a number of issues that I fixed-up
>
> Thanks for catching the scsi bugs! It was getting late yesterday night, so
> I didn't go through a full allyesconfig then.
>
> > I pushed these to my own new linus-bkl tree.
> > git://www.kernel.org/pub/scm/linux/kernel/git/jkacur/jk-2.6.git linux-bkl
> >
> > Frederic, if you want to grab those, pls do so. also, we might want to combine
> > my compile fixes with Arnd's push-down patches, for better git bisectability.
>
> Yes, your fixes (except the v4l2 patch, see comment there) should best be
> merged into the main patches.
>
> The idea was that if we manage to kill all fops->ioctl users right away,
> we wouldn't even need Linus' patch and move to dungeon level 2 directly.
> Either way works for me though.
>
> Should we just split up the rest? If you, Frederic and me each take one
> of these chunks, we're done. According to the diffstat from Linus' patch,
> this is what's left:
Okay - good plan. I AM trying to balance doing my own day-to-day work,
and writing slides for a conference but I'm sure you and Frederic are
just as pressed for time as me, so lets go-ahead and divide it up!
That will prevent us from doing redundant work.
I assume the target is 2.6.35 so, we have a little bit of time anyway.
I suggest we divide up a) and b) first and postone c) until the first
parts are done.
Arranging our names by alphabetical order and shuffling the files
off one at a time (for variety), I get this. Is everybody happy with that?
36 files / 3 = 12 files each.
Jan - speak up if you want in.
Arnd
----
arch/cris/arch-v10/drivers/ds1302.c
arch/cris/arch-v10/drivers/pcf8563.c
arch/cris/arch-v32/drivers/i2c.c
arch/cris/arch-v32/drivers/pcf8563.c
arch/ia64/sn/kernel/sn2/sn_hwperf.c
arch/m68k/mvme16x/rtc.c
arch/um/drivers/mmapper_kern.c
fs/coda/psdev.c
fs/hfsplus/dir.c
fs/logfs/file.c
fs/ntfs/dir.c
fs/smbfs/file.c
Frederic
--------
arch/cris/arch-v10/drivers/gpio.c
arch/cris/arch-v10/drivers/sync_serial.c
arch/cris/arch-v32/drivers/mach-a3/gpio.c
arch/cris/arch-v32/drivers/sync_serial.c
arch/m68k/bvme6000/rtc.c
arch/um/drivers/harddog_kern.c
fs/autofs/root.c
fs/fat/dir.c
fs/hfsplus/inode.c
fs/ncpfs/dir.c
fs/ntfs/file.c
fs/udf/dir.c
John
----
arch/cris/arch-v10/drivers/i2c.c
arch/cris/arch-v32/drivers/cryptocop.c
arch/cris/arch-v32/drivers/mach-fs/gpio.c
arch/ia64/kernel/perfmon.c
arch/m68k/bvme6000/rtc.c
arch/um/drivers/hostaudio_kern.c
fs/coda/pioctl.c
fs/fat/file.c
fs/logfs/dir.c
fs/ncpfs/file.c
fs/smbfs/dir.c
fs/udf/file.c
>
> a) arch specific drivers
> arch/cris/arch-v10/drivers/ds1302.c | 2 +-
> arch/cris/arch-v10/drivers/gpio.c | 2 +-
> arch/cris/arch-v10/drivers/i2c.c | 2 +-
> arch/cris/arch-v10/drivers/pcf8563.c | 2 +-
> arch/cris/arch-v10/drivers/sync_serial.c | 2 +-
> arch/cris/arch-v32/drivers/cryptocop.c | 2 +-
> arch/cris/arch-v32/drivers/i2c.c | 2 +-
> arch/cris/arch-v32/drivers/mach-a3/gpio.c | 2 +-
> arch/cris/arch-v32/drivers/mach-fs/gpio.c | 2 +-
> arch/cris/arch-v32/drivers/pcf8563.c | 2 +-
> arch/cris/arch-v32/drivers/sync_serial.c | 2 +-
> arch/ia64/kernel/perfmon.c | 2 +-
> arch/ia64/sn/kernel/sn2/sn_hwperf.c | 2 +-
> arch/m68k/bvme6000/rtc.c | 2 +-
> arch/m68k/mvme16x/rtc.c | 2 +-
> arch/um/drivers/harddog_kern.c | 2 +-
> arch/um/drivers/hostaudio_kern.c | 4 +-
> arch/um/drivers/mmapper_kern.c | 2 +-
>
> b) file systems (my other series has patches for some of these already)
> fs/autofs/root.c | 2 +-
> fs/autofs4/root.c | 2 +-
> fs/coda/pioctl.c | 2 +-
> fs/coda/psdev.c | 2 +-
> fs/fat/dir.c | 2 +-
> fs/fat/file.c | 2 +-
> fs/hfsplus/dir.c | 2 +-
> fs/hfsplus/inode.c | 2 +-
> fs/logfs/dir.c | 2 +-
> fs/logfs/file.c | 2 +-
> fs/ncpfs/dir.c | 2 +-
> fs/ncpfs/file.c | 2 +-
> fs/ntfs/dir.c | 2 +-
> fs/ntfs/file.c | 2 +-
> fs/smbfs/dir.c | 2 +-
> fs/smbfs/file.c | 2 +-
> fs/udf/dir.c | 2 +-
> fs/udf/file.c | 2 +-
>
> c) special stuff (this should go last)
> Documentation/filesystems/vfs.txt | 2 +-
> fs/bad_inode.c | 2 +-
> fs/ioctl.c | 4 +-
> fs/compat_ioctl.c | 2 +-
> fs/ecryptfs/file.c | 9 ++++---
> fs/proc/inode.c | 8 +++---
> include/linux/fs.h | 2 -
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2010-04-27 12:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 9:18 [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes John Kacur
2010-04-27 9:18 ` [PATCH 01/10] dvb: push down BKL into ioctl functions John Kacur
2010-04-27 9:18 ` [PATCH 02/10] scsi: " John Kacur
2010-04-27 9:18 ` [PATCH 03/10] bkl: Fix up compile problems in megaraid from bkl push-down John Kacur
2010-04-27 9:18 ` [PATCH 04/10] bkl: Fix missing inode tw_chrdev_ioctl due to bkl pushdown John Kacur
2010-04-27 9:18 ` [PATCH 05/10] bkl: Fix missing inode in twl_chrdev_ioctl resulting from " John Kacur
2010-04-27 9:18 ` [PATCH 06/10] isdn: push down BKL into ioctl functions John Kacur
2010-04-27 9:18 ` [PATCH 07/10] staging: " John Kacur
2010-04-27 9:18 ` [PATCH 08/10] v4l: always use unlocked_ioctl John Kacur
2010-04-27 9:18 ` [PATCH 09/10] drivers: push down BKL into various drivers John Kacur
2010-04-27 9:18 ` [PATCH 10/10] bkl: Fix-up compile problems as a result of the bkl-pushdown John Kacur
2010-04-27 11:17 ` Arnd Bergmann
2010-04-27 11:54 ` John Kacur
2010-04-27 13:03 ` Arnd Bergmann
2010-04-28 12:24 ` Mauro Carvalho Chehab
2010-04-28 12:37 ` Hans Verkuil
2010-04-28 13:02 ` Laurent Pinchart
2010-04-28 14:46 ` Mauro Carvalho Chehab
2010-04-28 14:55 ` Linus Torvalds
2010-04-28 21:52 ` Frederic Weisbecker
2010-04-29 3:42 ` [PATCH 0/5] Pushdown bkl from v4l ioctls Frederic Weisbecker
2010-04-29 6:44 ` Hans Verkuil
2010-04-29 7:10 ` Laurent Pinchart
2010-04-29 7:38 ` Arnd Bergmann
2010-05-01 9:55 ` Hans Verkuil
2010-05-01 10:47 ` Arnd Bergmann
2010-05-01 14:58 ` Frederic Weisbecker
2010-05-01 11:11 ` Alan Cox
2010-04-29 3:42 ` [PATCH 1/5] v4l: Pushdown bkl into video_ioctl2 Frederic Weisbecker
2010-04-29 3:42 ` [PATCH 2/5] v4l: Use video_ioctl2_unlocked from drivers that don't want the bkl Frederic Weisbecker
2010-04-29 3:42 ` [PATCH 3/5] v4l: Change users of video_ioctl2 to use unlocked_ioctl Frederic Weisbecker
2010-04-29 3:42 ` [PATCH 4/5] v4l: Pushdown bkl to drivers that implement their own ioctl Frederic Weisbecker
2010-04-29 3:42 ` [PATCH 5/5] v4l: Remove struct v4l2_file_operations::ioctl Frederic Weisbecker
2010-04-27 11:31 ` [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes Arnd Bergmann
2010-04-27 12:19 ` John Kacur [this message]
2010-04-27 12:41 ` Frederic Weisbecker
2010-04-27 14:24 ` [PATCH 0/6] BKL pushdown into ioctl, continued Arnd Bergmann
2010-04-27 14:24 ` [PATCH 1/7] logfs: push down BKL into ioctl function Arnd Bergmann
2010-04-27 14:32 ` Arnd Bergmann
2010-04-27 14:58 ` Jörn Engel
2010-04-27 15:05 ` Arnd Bergmann
2010-04-27 15:09 ` Jörn Engel
2010-04-27 15:27 ` John Kacur
2010-04-27 15:32 ` Jörn Engel
2010-04-27 15:38 ` Arnd Bergmann
2010-04-27 20:12 ` Frederic Weisbecker
2010-04-27 20:30 ` [PATCH] logfs: kill BKL Arnd Bergmann
2010-05-19 12:51 ` Frederic Weisbecker
2010-04-27 15:36 ` [PATCH 1/7] logfs: push down BKL into ioctl function Linus Torvalds
2010-04-27 16:29 ` John Kacur
2010-04-27 19:59 ` Frederic Weisbecker
2010-04-27 14:24 ` [PATCH 2/7] hfsplus: " Arnd Bergmann
2010-04-27 14:24 ` [PATCH 3/7] cris: push down BKL into some device drivers Arnd Bergmann
2010-04-27 17:22 ` Frederic Weisbecker
2010-04-30 7:53 ` Jesper Nilsson
2010-05-17 2:51 ` Frederic Weisbecker
2010-04-27 14:24 ` [PATCH 4/7] sn_hwperf: kill BKL usage Arnd Bergmann
2010-04-27 14:24 ` [PATCH 5/7] um/mmapper: remove " Arnd Bergmann
2010-04-27 14:24 ` [PATCH 6/7] coda/psdev: remove BKL from ioctl function Arnd Bergmann
2010-04-27 14:24 ` [PATCH 7/7] smbfs: push down BKL into " Arnd Bergmann
2010-04-27 12:40 ` [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes Frederic Weisbecker
2010-04-27 12:51 ` Geert Uytterhoeven
2010-04-28 21:18 ` Frederic Weisbecker
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=alpine.LFD.2.00.1004271359180.3318@localhost \
--to=jkacur@redhat.com \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=jblunck@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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