On Mon, Aug 15, 2005 at 11:08:04AM -0700, Nishanth Aravamudan wrote:
> Description: Use schedule_timeout_{,un}interruptible() instead of
> set_current_state()/schedule_timeout() to reduce kernel size. Also use
> helper functions to convert between human time units and jiffies rather
> than constant
On Mon, Aug 15, 2005 at 11:40:13AM -0700, Nishanth Aravamudan wrote:
> Hrm, I got dropped from the Cc list...? No worries, I'm subscribed in
> two places :)
I didn't do that manually, must haven some mail header thing.
> I think your reference to "last time" is the KJ patches which probably
> use
On Mon, Aug 15, 2005 at 04:32:53PM -0500, James Bottomley wrote:
> On Mon, 2005-08-15 at 16:22 -0500, mikem wrote:
> > +#ifdef CONFIG_IA64
> > +case BLKGETLASTSECT:
> > +case BLKSETLASTSECT:
> > +#endif
> > return blk_ioctl(inode->i_rdev, cmd, arg);
>
> What makes these
On Tue, Aug 16, 2005 at 11:11:06AM +0200, Rolf Eike Beer wrote:
> cpqfcTS_reset() is never referenced from anywhere. By using the nonexistent
> constant SCSI_RESET_ERROR it causes just another unneeded compile error.
That was the old reset handler. Do you actually have this hardware?
The driver
What's AS UP1 in your subject?
On Tue, Aug 16, 2005 at 03:37:07PM +0530, shahid shaikh wrote:
> Hi all,
> While doing insmod for a psuedo driver, kernel is dumping a stack because
> sleep function is called.
> My init_module function for psuedo driver calls add_disk to register admin
> device.
> I
On Tue, Aug 16, 2005 at 06:20:56PM +0200, Rolf Eike Beer wrote:
> Use pid of worker thread and struct completion for signaling end of worker
> thread (code more or less taken from drivers/net/8139too.c). For the moment
> the return code of the start/stop functions is ignored, this will change
>
On Tue, Aug 16, 2005 at 02:48:13PM -0400, Neil Horman wrote:
> Patch to clean up missing overflow check in get_blkdev_list. the printf which
> adds the "Block Devices" string in /proc/devices can overflow the presented
> page
> if get_chrdev_list eats up the entire 4k space. Tested by myself, wit
On Wed, Aug 17, 2005 at 04:07:03AM +0900, Machida, Hiroyuki wrote:
>
> This is a take 2 of posix file attribute support on VFAT.
Sorry, but this is far too scary. Please just use one of the sane
filesystems linux supports.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> >I concur, in fact we should really kill that thing off entirely.
>
> I'm all for killing it off entirely but got some feedback that on
> i386 segment.h can be included by userspace programs.
No kernel headers can be included by user
On Wed, Aug 17, 2005 at 10:56:24AM +0200, Miklos Szeredi wrote:
> > On Wed, Aug 17, 2005 at 12:43:37AM -0500, Kumar Gala wrote:
> > > >I concur, in fact we should really kill that thing off entirely.
> > >
> > > I'm all for killing it off entirely but got some feedback that on
> > > i386 segment
On Wed, Aug 17, 2005 at 11:15:39AM +0200, Miklos Szeredi wrote:
> They are provided by _one_ kernel, not necessarily the running kernel.
No, they're provided by packages like glibc-kernheaders or similar
that are maintained separately. They're split from the kernel headers
and we don't need to ke
> +static inline int pte_user(pte_t pte)
> + { return (pte).pte_low & _PAGE_USER; }
Once you start reformatting things please make sure the result version
matches the documented codingstyle. That would be:
static inline int pte_user(pte_t pte)
{
return (pte).pte_low & _PAGE_USER;
}
On Mon, Apr 18, 2005 at 12:20:31PM +0900, Takashi Ikebe wrote:
> The patch was over 50k, so I separate it to each architecture and in line..
>
> This patch add function called "Live patching" which is defined on
> OSDL's carrier grade linux requiremnt definition to linux 2.6.11.7 kernel.
Traditio
On Mon, Apr 18, 2005 at 12:47:11PM +0400, Artem B. Bityuckiy wrote:
> JFFS2 assumes that the above mentioned 'state' field is always coherent
> with the real state of the inode. The state is changed on read_inode()
> and clear_inode() inode operation calls.
> One obvious thing to fix this JFFS2 p
On Mon, Apr 18, 2005 at 12:58:50PM +0400, Artem B. Bityuckiy wrote:
> On Mon, 2005-04-18 at 09:51 +0100, Christoph Hellwig wrote:
> > No, exporting locks is a really bad idea. Please try to find a better
> > method to fix your problem that doesn't export random kernel symbol
> Mingming Cao <[EMAIL PROTECTED]> said:
> The ext2 handle discard preallocation differently at that time, it discard the
> preallocation at each iput(), not in input_final(), so we think it's
> unnecessary to thrash it so frequently, and the right thing to do, as we did
> for ext3 reservation, dis
On Mon, Apr 18, 2005 at 03:46:21PM +0400, Artem B. Bityuckiy wrote:
> On Mon, 2005-04-18 at 11:53 +0100, Christoph Hellwig wrote:
> > The VFS already has a method for freeing an struct inode pointer, and that
> > is ->destroy_inode. You're probably better off updating your
On Mon, Apr 18, 2005 at 04:31:06PM +0400, Artem B. Bityuckiy wrote:
> On Mon, 2005-04-18 at 12:52 +0100, Christoph Hellwig wrote:
> > Oh, I thought the problem is that JFFS2 thought an inode was freed when
> > it still was in use. So you're problem is actually that it's n
With the upcoming merge of the current SCSI development branch (probably
after the 2.6.12 release), Linux will have more advanced Fibre Channel
support than any currently available operating system.
The new Fibre Channel (FC) transport class offers two major advantages
over traditional standalone
This looks like a patch for Linux 2.4. Such major changes for the
2.4 tree don't make sense anymore, especially for functionality not
even in Linux 2.6.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, Apr 18, 2005 at 12:20:06PM -0400, Igor Shmukler wrote:
> I don't think that drivers have to be architecture independent. Why is
> this a problem?
Actually, yes a driver should generally be architecture independent.
There's some exception for things dealing with lowlevel architecture-
depen
On Mon, Apr 18, 2005 at 11:22:29AM -0500, Timur Tabi wrote:
> That's not what we're seeing. We have hardware that does DMA over the
> network (much like the Infiniband stuff), and we have a testcase that fails
> if get_user_pages() is used, but not if mlock() is used.
If you don't share your te
On Mon, Apr 18, 2005 at 07:38:57PM +0200, Lorenzo Hern?ndez Garc?a-Hierro wrote:
> Enforces the RLIMIT_NPROC limit by adding an additional check for
> execve(), as
> such limit is checked only during fork() calls.
What's the point? exec doesn't create new process and exec() shouldn't
start to fail
On Tue, Apr 19, 2005 at 10:47:30AM +0200, Olivier Galibert wrote:
> ...or more importantly, is it allowed. Kernel is FC3 2.6.10-1.766.
Yes, it's allowed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, Apr 19, 2005 at 11:24:31AM +0200, Olivier Galibert wrote:
> > Yes, it's allowed.
>
> Thanks. Pages in that case are continuous then, right?
Good question actually. I know XFS does passed vmalloc'ed memory down
the block I/O path, but that's as a scatter/gather request. All non-s/g
requ
On Wed, Apr 20, 2005 at 04:15:26AM +0200, Adrian Bunk wrote:
> This patch contains the following possible cleanups:
> - make needlessly global functions static
> - remove unused code
Not sure it's worth doing much on this, as the driver is beeing
obsoleted by the skge driver.
-
To unsubscribe from
On Thu, Apr 21, 2005 at 11:58:12AM +0200, Geert Uytterhoeven wrote:
> sun3_NCR5380.c still uses the following:
>
> - SCSI_ABORT_SUCCESS
> - SCSI_ABORT_ERROR
> - SCSI_ABORT_SNOOZE
> - SCSI_ABORT_BUSY
> - SCSI_ABORT_NOT_RUNNING
> - SCSI_RESET_SUCCESS
> - SCSI_RESET_BUS_RESET
>
> causi
On Fri, Apr 22, 2005 at 05:02:38PM +0200, Martin Schwidefsky wrote:
> +#if defined(CONFIG_DASD_CMB) || defined(CONFIG_DASD_CMB_MODULE)
> +COMPATIBLE_IOCTL(BIODASDCMFENABLE)
> +COMPATIBLE_IOCTL(BIODASDCMFDISABLE)
> +COMPATIBLE_IOCTL(BIODASDREADALLCMB)
> +#endif
I don't think that there should be if
On Sun, Jul 03, 2005 at 01:30:23PM +0100, Hugh Dickins wrote:
> > this way we don't need to put a lot of __slow's in the code *and* it's
> > based on measurements not assumptions, and can be tuned for a specific
> > situation in addition.
>
> This is reminiscent of "fur", whose source Old SCO open
On Sun, Jul 03, 2005 at 08:42:24PM -0700, Hans Reiser wrote:
> >>Right. But, /proc started somewhere, didn't it?
> >>
> >>
> >
> >Sun.
> >
> >
> No, plan 9.
Almost on the right track, it was v8, two steps before plan9. But that's
just the process-part of procfs, not the big mess we have no
On Tue, Jul 05, 2005 at 06:43:31PM -0400, Jeremy Maitin-Shepard wrote:
> > Let's say cryptocompress gets implemented. Not all of userland
> > rewritten, not even any of userland rewritten, just a cryptocompress
> > plugin for the kernel. And instead of having to learn a new tool, I can
> > just b
We can just kill the driver again, mainline now has the proper ide-layer
driver for the hardware. The scsi-layer driver is not going in with any
amount of cleanups, it's just conceptually wrong.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Jul 06, 2005 at 03:18:03PM -0700, Mark Fasheh wrote:
> Resending this series as I haven't heard anything back from anyone...
> If there's no objections, can we get this into -mm for some additional
> review and testing?
The patches are fine, thanks.
-
To unsubscribe from this list: send t
On Thu, Jul 07, 2005 at 11:58:39AM +0200, Andrew Victor wrote:
> While he seems generally happy with most of the code, he has doubts
> about merging the Atmel-supplied headers and suggested I post this to
> the linux-kernel list for a wider review.
>
> While I agree that their usage of structs/cod
On Sat, Jul 02, 2005 at 05:15:16PM -0400, Karim Yaghmour wrote:
> Christoph Hellwig wrote:
> > This code is rather pointless. The ltt_mux is doing all the real
> > work and it's not included. And while we're at it the layering for
> > it is wrong aswell -
this is missing a description. But I don't think that one is gonna help, we're
not gonna add truckloads of crap just to print a warning when a user shoots
himself
in his foot.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
no explanation and even the subject doesn't match patch contents..
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/l
So what is this doing, and is it breaking swsusp support?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
So what's this deep magic doing? And why do you add such crude function for
debug pagealloc builds only?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Pleas
Please add an explanation why this is nessecary. Big NACK for the patch as-is,
but
to find a proper solution we need to know what you're actually doing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
UI support is nothing that belongs here. People won't die by having a text
console for
a while.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read t
This submissions is completely useless. 48 patches without description
and a subbject lines that hides the little information even more.
Please start again, and only with useful patches that on their own,
against -mm and with detailed explanations of each patch.
-
To unsubscribe from this list:
Please send new crytptoapi algorithms to the cryptoapi maintainers for review.
It's something that's completely independent of any software suspend stuff.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Again, why do you think you need this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Jul 28, 2005 at 11:43:41PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Someone mentioned the mess in evdev.c that is caused by the fact that the
> structures that are passed to/from user mode via read/write require
> conversion when this API is used from 32 bit tasks on 64 bit kernels.
>
On Thu, Jul 28, 2005 at 08:57:23AM -0500, [EMAIL PROTECTED] wrote:
> v9fs: add file-descriptor based transport as was requested by LANL and
> Plan 9 from User Space folks.
Couldn't the two other transports be implemented ontop of this one using
a mount helper doing the pipe or tcp setup?
-
To uns
On Fri, Jul 29, 2005 at 01:13:07AM +1000, Stephen Rothwell wrote:
> On Thu, 28 Jul 2005 16:02:58 +0100 Christoph Hellwig <[EMAIL PROTECTED]>
> wrote:
> >
> > > And where were you a week ago when I asked if I should post this patch?
> >
> > A :-) Can'
> And where were you a week ago when I asked if I should post this patch?
A :-) Can't remember it at all, maybe you forgot that we mere mortals can't
read linux-arch@vger.kernel.org ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
doesn't make the local irq disabling around it less buggy, but at least
we replace the offender with the right kind of primitive.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/acorn/blo
this is the last serial driver not using initcalls.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/char/tty_io.c
===
--- linux-2.6.orig/drivers/char/tty_io.c2005-06-26 13:26:22.000
On Sat, Jul 30, 2005 at 08:52:26PM +0200, Sam Ravnborg wrote:
> Please - use tabs for indention, not for alignment.
> The below would look rather messy with tabs=4.
> Almost everywhere tabs are used in Makefiles it is plina wrong.
> Tabs are brillient for indention but you cannot just assume 8 spac
On Sat, Jul 30, 2005 at 11:36:22AM -0700, Alex Aizman wrote:
> OK. Hopefully that'll remain.
Please ask davem for a netlink number allocation.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vge
On Sat, Jul 30, 2005 at 07:24:46PM -0400, Jeff Garzik wrote:
>
> If this is post-2.6.13 material, that's fine.
>
> I've been getting tired of the slow movement of wireless. A little bit
> of that is my fault, certainly. I've also been wanting to get these net
> drivers out to Linux users.
>
On Tue, Jul 12, 2005 at 10:23:17AM +0200, Thomas Heinz wrote:
> Hi Christoph
>
> You wrote:
> >While adding support for partitions on sr is trivial it has a huge
> >drawback: it's chaning the dev_t space by using up device numbers
> >for partitions, so /dev/sr0 ff will have different device number
So folks, this is still in 2.6.13-rc4, shouldn't we pull it out so we
don't add an interface soon to be removed again to 2.6.13?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/maj
On Tue, Aug 02, 2005 at 02:31:55PM +0200, Martin Drab wrote:
> Hmm. I see. So perhaps you may ask someone (James, Christoph, ...?) to
> revert that patch, because the scsi_cmnd->state is needed here for this
> purpose.
Not, it's not. Use of that field wouldn't have passed review.
-
To unsubscri
On Tue, Aug 02, 2005 at 02:29:36PM -0700, Bruce Allan wrote:
> [resending to Neil, Trond and linux-nfs list; initial copy to lkml]
>
> When registering an RPC cache, cache_register() always sets the owner as
> the sunrpc module. However, there are RPC caches owned by other modules.
> With the in
On Thu, Aug 18, 2005 at 12:01:52PM +0200, Folkert van Heusden wrote:
> What about a zero-copy read-interface?
> An ioctl (or something) which enables the kernel to do dma directly to
> the userspace. Of course this should be limited to the root-user or a
> user with special capabilities (rights) si
On Thu, Aug 18, 2005 at 02:07:14AM +0200, Jesper Juhl wrote:
> This patch renames sema_init to init_sema, init_MUTEX to init_mutex and
> init_MUTEX_LOCKED to init_mutex_locked and at the same time creates 3
> (deprecated) wrapper functions with the old names.
What's the point? There's not need
Please stop spamming lkml about openafs, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Aug 18, 2005 at 09:48:00PM -0400, Lee Revell wrote:
> What ever happened with cpuinfo(1)? This thread:
>
> http://64.233.161.104/search?q=cache:_uCmn69gfyoJ:lists.debian.org/lsb-discuss/2002/01/msg00084.html+cpuinfo&hl=en
>
> ended inconclusively.
LSB people apparently didn't care. Giv
On Fri, Aug 19, 2005 at 02:23:11PM +0530, Mukund JB`. wrote:
> Dear all,
>
> Its time that there should be a fix applied to the FAT12 subsystem in
> Linux.
> I have noted that removable device FAT12 formatted in Camera like
> digital media does NOT have the FAT12 in sector 0 instead it has a
> par
On Fri, Aug 19, 2005 at 06:40:36PM +0200, Adrian Bunk wrote:
> <-- snip -->
>
> ...
> LD drivers/scsi/aic7xxx/built-in.o
> drivers/scsi/aic7xxx/aic79xx.o: In function `aic_parse_brace_option':
> : multiple definition of `aic_parse_brace_option'
> drivers/scsi/aic7xxx/aic7xxx.o:: first def
On Fri, Aug 19, 2005 at 07:02:18PM +0100, Al Viro wrote:
> On Fri, Aug 19, 2005 at 05:53:32PM +0100, Al Viro wrote:
> > I'm taking NFS helpers to libfs.c and switching ncpfs to them. IMO that's
> > better than copying the damn thing and other network filesystems might have
> > the same needs event
On Fri, Aug 19, 2005 at 08:43:06PM +0100, Al Viro wrote:
> On Fri, Aug 19, 2005 at 08:41:29PM +0100, Matthew Wilcox wrote:
> > > is getting crowded. Linus, do you have any objections to that or
> > > suggestions
> > > on filename here?
> >
> > fs/symlink.c?
>
> Or fs/lib/symlink.c...
That's a
> diff --git a/drivers/char/extint.c b/drivers/char/extint.c
> new file mode 100644
> --- /dev/null
> +++ b/drivers/char/extint.c
> @@ -0,0 +1,673 @@
> +/*
> + * This file is subject to the terms and conditions of the GNU General Public
> + * License. See the file "COPYING" in the main directory o
> +config EXTINT_SGI_IOC4
> + tristate "Device driver for SGI IOC4 external interrupts"
> + depends on (IA64_GENERIC || IA64_SGI_SN2) && EXTINT && BLK_DEV_SGIIOC4
Is the ioc4 core abstraction config symbol really BLK_DEV_SGIIOC4?
That probably wants fixing in a separate patch.
> + T
On Mon, Aug 22, 2005 at 06:20:56PM +0200, Adrian Bunk wrote:
> I didn't find any modular usage in the kernel.
And there shouldn't be one either. This is really just for some syscalls,
everything else should use get_super based on a struct block_device. If
there's any caller using this wrongly in
On Mon, Aug 22, 2005 at 02:43:30PM -0700, Andrew Morton wrote:
> > Laughter was not wholly unexpected, though I wasn't joking. I'm trying
> > to be realistic about the lifetime of any given hardware, and IOC4 is
> > several years old at this point. Couple that with a sincere desire to
> > preserv
On Tue, Aug 23, 2005 at 11:46:33AM +0300, Pekka J Enberg wrote:
> As noticed by Dmitry Torokhov, write() can not return ENOMEM:
>
> http://www.opengroup.org/onlinepubs/95399/functions/write.html
>
> Therefore fixup generic_file_buffered_write() in mm/filemap.c (pointed out by
> Nathan Scott).
On Tue, Aug 23, 2005 at 02:50:17PM +0200, Pavel Machek wrote:
> - DRI being used in X where the drivers don't properly support
> suspend/resume (NVidia esp)
NVidias driver is not support and a copyright violation of the
copyrights of many of use. It's never supported so please don't
mention it.
On Tue, Aug 23, 2005 at 03:00:50PM +0200, Pavel Machek wrote:
> Hi!
>
> > > - DRI being used in X where the drivers don't properly support
> > > suspend/resume (NVidia esp)
> >
> > NVidias driver is not support and a copyright violation of the
> > copyrights of many of use. It's never supported
On Tue, Aug 23, 2005 at 10:24:30PM +0200, Miklos Szeredi wrote:
> Remove unused ia_attr_flags from struct iattr, and related defines.
I had actually planned to make use of this, by adding a common helper
for the ext2-style file flags ioctl so all the checking is moved outside
the filesystems. OTO
On Tue, Aug 23, 2005 at 10:43:35PM +0200, Miklos Szeredi wrote:
> 64 bit architectures all implement their own compatibility sys_open(),
> when in fact the difference is simply not forcing the O_LARGEFILE
> flag. So use the a common function instead.
Traditional naming would be just do_open(), bu
On Tue, Aug 23, 2005 at 10:47:07PM +0100, Al Viro wrote:
> alpha xchg has to be a macro - alpha disables always_inline and if that
> puppy does not get inlined, we immediately blow up on undefined reference.
> Happens even on gcc3; with gcc4 that happens a _lot_.
I think you should rather fix alph
> > > +static int extint_counter_open(struct inode *inode, struct file *filp)
> > > +{
> > > + struct extint_device *ed = file_to_extint_device(filp);
> >
> > you don't need the file but just the inode (strictly speaking the cdev),
> > and doing this based on the file is rather confusing to the re
Please don't announce propitarty drivers on lkml, thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, Aug 24, 2005 at 02:17:11AM -0400, Jeff Garzik wrote:
>
> Difficulty: beginner / intermediate
>
> Modern network drivers have a per-NIC list of debugging messages that
> can be enabled/disabled at runtime, implemented as a bitmask named
> 'msg_enable' in each driver. VERY useful for tr
On Wed, Aug 24, 2005 at 11:00:07AM +0200, Miklos Szeredi wrote:
> > On Tue, Aug 23, 2005 at 10:43:35PM +0200, Miklos Szeredi wrote:
> > > 64 bit architectures all implement their own compatibility sys_open(),
> > > when in fact the difference is simply not forcing the O_LARGEFILE
> > > flag. So us
On Wed, Aug 24, 2005 at 10:57:50AM +0200, Adrian Bunk wrote:
> If #includ'ing interrupt.h should be enough for getting the prototype of
> e.g. enable_irq() on all architectures, we need this patch.
Per defintion you need to include right now. I'd like to change
that to , but not my including t
On Wed, Aug 24, 2005 at 11:09:38AM -0300, Rafael Esp?ndola wrote:
> On 8/24/05, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> > Please don't announce propitarty drivers on lkml, thanks.
> Sorry, but my intent with this drivers is to make them as free as
> possible. I
On Wed, Aug 24, 2005 at 11:55:20AM +0200, Frederik Schueler wrote:
> Hello,
>
> On Tue, Aug 23, 2005 at 01:00:40PM -0700, Patrick Mansfield wrote:
> > The use of scsiadd script implies that you are attaching or somehow
> > modifying the storage after the driver has loaded. Is that correct?
>
> ye
On Wed, Aug 24, 2005 at 02:48:03PM +0200, Frederik Schueler wrote:
> Hello,
>
> On Wed, Aug 24, 2005 at 11:01:12AM +0100, Christoph Hellwig wrote:
> > > yes exactly, only the bootdrive LUN is registered after bootup. I have
> > > to selectively scsiadd the other LUNs if
On Thu, Aug 25, 2005 at 10:45:12AM +0200, Eric Dumazet wrote:
> This patch assumes that atomic_read() is a plain {return v->counter;} on
> all architectures. (keywords : sysctl, /proc/sys/fs/file-nr, proc_dointvec)
But that's not true. You need to write you own sysctl handler for it,
probably wo
On Thu, Aug 25, 2005 at 11:17:23AM +0200, Eric Dumazet wrote:
> >But that's not true. You need to write you own sysctl handler for it,
> >probably worth adding a generic atomic_t sysctl handler while you're
> >at it.
> >
>
> I checked linux-2.6.13-rc7 tree, and atomic_read() is just a wrapper to
On Thu, Aug 25, 2005 at 02:24:56AM -0700, Zachary Amsden wrote:
> Yes, agree totally, i386 _requires_ asm/segment.h. It is used in
> low-level trap handling and bootup code from assembly files. In
> addition,
but keeping the header under that name will just encorage people
to put it back into
On Thu, Aug 25, 2005 at 01:24:40AM -0700, Andrew Morton wrote:
> > IMO sys_readahead() doesn't make sense if the file is opened with
> > O_DIRECT, because the page cache is stuffed but never used. Therefore
> > this patch changes that by letting the call return with -EINVAL.
> >
>
> a) It doesn't
On Fri, Aug 26, 2005 at 12:51:30AM +1000, Nick Piggin wrote:
> Eric Dumazet wrote:
> >Nick Piggin a ?crit :
> >
>
> >>Would you just be able to add the atomic sysctl handler that
> >>Christoph suggested?
> >>
> >
> >Quite a lot of work indeed, and it would force to convert 3 int
> >(nr_files, nr_
On Thu, Aug 25, 2005 at 11:49:35PM +0530, Dipankar Sarma wrote:
> On Thu, Aug 25, 2005 at 05:13:05PM +0200, Eric Dumazet wrote:
> > Nick Piggin a ?crit :
> >
> > >OK, well I would prefer you do the proper atomic operations throughout
> > >where it "really matters" in file_table.c, and do your lazy
On Thu, Aug 25, 2005 at 02:07:38PM +0100, Al Viro wrote:
> Fine, as long as that merge is done before your s/thread_info/stack/ patches.
> It should be the first step before doing 200Kb worth of cosmetical stuff
> that affects every architecture out there, not something that depends on
> it done.
>
> > typedef struct _CSMI_SAS_IDENTIFY {
> >__u8 bDeviceType;
> >__u8 bRestricted;
> >__u8 bInitiatorPortProtocol;
> >__u8 bTargetPortProtocol;
> >__u8 bRestricted2[8];
> >__u8 bSASAddress[8];
> >__u8 bPhyIdentifier;
> >__u8 bSignalClass;
> >__u8 bReserve
On Fri, Aug 26, 2005 at 01:00:19PM +0200, Karel Zak wrote:
>
> http://people.redhat.com/kzak/util-linux-cryptsetup
>
> It's the place where you can found util-linux patch that adds full
> cryptsetup-luks support to mount, umount, swapon and swapoff. The patch
> supports classic cryptsetup and LU
On Thu, Aug 11, 2005 at 07:37:17PM +0200, Christoph Hellwig wrote:
> On Tue, Aug 09, 2005 at 11:10:03PM +0200, Christoph Hellwig wrote:
> > Currently snsc_event for Altix systems sends SIGPWR to init (and abuses
> > tasklist_lock..) while the sbus drivers call execve for /sbin/shut
ht be might unloadable more easily aswell.
The new code uses read_lock instead of read_lock_irq because the
tasklist_lock only needs irq disabling for writers.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/block/cf
es in
later patches.
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Index: linux-2.6/arch/arm/kernel/ptrace.c
===
--- linux-2.6.orig/arch/arm/kernel/ptrace.c 2005-08-14 12:03:16.0
+0200
+++ linux-2.6/arch/arm/kern
covered are:
- m68k: has some large ptrace changes pending, should be converted to
the common sys_ptrace later
- ia64 (native ptrace only): does some wierd stuff about finding a
different thread in the same threadgroup
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
On Mon, Aug 29, 2005 at 12:32:35PM +0200, Henrik Brix Andersen wrote:
> On Sat, 2005-08-13 at 15:21 -0700, Linus Torvalds wrote:
> > Doesn't seem to be serious enough to be worth it at this late stage in the
> > 2.6.13 game. Can you re-send after I do a release?
>
> Resending as requested:
>
> H
Looks pretty good to me. Small issues I've identified:
- what do you need the hba_count attribute for? This should be
implementable in userspace pretty easily by iterating of all
devices of the scsi_host class that are attached to the driver
- the ->queuecommand cleanup patch I sent you
On Thu, Aug 25, 2005 at 05:38:24PM -0400, Bagalkote, Sreenivas wrote:
> Hello All,
>
> After a couple of false starts early on, I am re-submitting the MegaRAID's
> SAS based RAID driver for your review.>
Your mailer seems to wrap lines and eat whitespaces..
-
To unsubscribe from this list: send
On Thu, Sep 01, 2005 at 03:49:18PM +0100, Alan Cox wrote:
> > - Why GFS is better than OCFS2, or has functionality which OCFS2 cannot
> > possibly gain (or vice versa)
> >
> > - Relative merits of the two offerings
>
> You missed the important one - people actively use it and have been for
> so
501 - 600 of 14612 matches
Mail list logo
