Pavel Machek wrote:
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be
Hi!
> So I guess all I have to do is:
> (A) Write a bunch of new syscall handlers taking
> arguments of the same types as the Darwin syscall
> handlers,
> (B) Figure out how to switch tables depending on the
> "syscall personality" of "current"
> (C) Figure out how to set the
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
> On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
> > When I said hibernate, I did mention it was to disk, not to ram.
>
> Suspend to disk is not trustable on Linux, and does not look like it
> will be any time soon. Suspend to
Hi Greg KH,
According to a Linux Journal article, you were the original author of the
usbfs_snoop patch, so I'm sending this patch to you.
When sending CONTROL URB's using the usual CONTROL ioctl, logging works
fine, but when sending them via SUBMITURB, like VMWare does, the
control fields are
Hi Ingo,
I built a parisc kernel with CONFIG_DEBUG_LOCKING_API_SELFTESTS enabled
recently, and got some interesting results:
double unlock: ok | ok |failed|WARNING at
/home/willy/merge-2.6/kernel/mutex-debug.c:83 debug_mutex_unlock()
Backtrace:
[<40144b38>]
On Fri, Dec 15, 2006 at 06:55:17PM -0800, Linus Torvalds wrote:
>
>
> On Sat, 16 Dec 2006, karderio wrote:
> >
> > As it stands, I believe the licence of the Linux kernel does impose
> > certain restrictions and come with certain obligations
>
> Absolutely. And they boil down to something very
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri, Dec 15, 2006 at 04:48:44PM -0500
> The "Re: Linux 2.6.20-rc1" sub-thread that had Jens and Alistair John
> Strachan replying seemed to implicate some core block layer badness.
>
The original problem (not mounting my raid6 partition) is observable
In-Reply-To: <[EMAIL PROTECTED]>
On Fri, 15 Dec 2006 16:37:15 -0500, Dave Jones wrote:
> > Can you enable CONFIG_USB_DEBUG and send the log info that happens right
> > before this oops?
>
> Gah, and here it is, actually attached this time.
> BUG: unable to handle kernel NULL pointer dereference
On Fri, 15 Dec 2006 23:46:28 -0500 Mike Accetta wrote:
> After upgrading an NFS client from 2.6.18 to 2.6.19 (and also with
> 2.6.19.1) we see a change in behavior of multiple NFS mounts against the
> same server (running 2.4.20 in this case). With 2.6.18 we could mount
> different pieces of
After upgrading an NFS client from 2.6.18 to 2.6.19 (and also with
2.6.19.1) we see a change in behavior of multiple NFS mounts against the
same server (running 2.4.20 in this case). With 2.6.18 we could mount
different pieces of the same remote file system with distinct read-only
and
On 12/16/06, jdow <[EMAIL PROTECTED]> wrote:
From: "Alexey Dobriyan" <[EMAIL PROTECTED]>
> On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
>> I think some kernel developers take to much responsibility, is there a
>> bug in a
>> binary driver? Send it upstream and explain to the
Linus, please pull from
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This tree is also available from kernel.org mirrors at:
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
for-linus
A couple of fixes for semi-nasty bugs on 32-bit
Regarding:
http://bugzilla.kernel.org/show_bug.cgi?id=7393
No closer to a solution yet. I'm worried about this problem because the
laptop is getting hotter than it's designed for and it is likely
shortening its life.
To aid in tracking it down, I could use reports of this problem
From: "Alexey Dobriyan" <[EMAIL PROTECTED]>
On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
I think some kernel developers take to much responsibility, is there a
bug in a
binary driver? Send it upstream and explain to the user that it's a
closed
source driver and is up to said
From: "Alan" <[EMAIL PROTECTED]>
blather and idiotic hogwash. "Information" doesn't want to be free, nor
is
it somethign you should fight for or necessarily even encourage.
As a pedant that is the one item I have to pick you up on Linus.
Information wants to be free, the natural efficient
On Fri, Dec 15, 2006 at 05:47:50PM -0800, Pete Zaitcev wrote:
> On Fri, 15 Dec 2006 16:37:15 -0500, Dave Jones <[EMAIL PROTECTED]> wrote:
>
> > Linux version 2.6.18-1.2864.fc6 ([EMAIL PROTECTED]) (gcc version 4.1.1
> > 20061011 (Red Hat 4.1.1-30)) #1 SMP Fri Dec 15 13:14:58 EST 2006
> >
On Sat, 16 Dec 2006, karderio wrote:
>
> As it stands, I believe the licence of the Linux kernel does impose
> certain restrictions and come with certain obligations
Absolutely. And they boil down to something very simple:
"Derived works have to be under the same license"
where the
Dear David and Forks:
I am a developer of Blackfin uClinux (blackfin.uclinux.org). After git clone
the latest Linus GIT tree and quilt the blackfin-uclinux patch list, I met
some problems related with your log2.h patches when I try to compile the
kernel. The compile log is listed as below:
On Fri, Dec 15, 2006 at 09:08:50PM -0500, Mike Frysinger wrote:
> On 12/12/06, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> >On Wed, Dec 06, 2006 at 06:03:50PM -0500, Mike Frysinger wrote:
> >> there are a plethora of headers that cannot be included straight due
> >> to the usage of __ types (like
Re :o)
On Fri, 2006-12-15 at 16:24 -0800, Linus Torvalds wrote:
>
> On Sat, 16 Dec 2006, karderio wrote:
> >
> > If the "free software community" has the clout to twist vendor's arms to
> > get them release driver source, then I'm all for it.
>
> I don't care what you're for, or what your
On 12/12/06, Adrian Bunk <[EMAIL PROTECTED]> wrote:
On Wed, Dec 06, 2006 at 06:03:50PM -0500, Mike Frysinger wrote:
> there are a plethora of headers that cannot be included straight due
> to the usage of __ types (like __u32) without first including
> linux/types.h ... so the question is,
On Sat, Dec 16, 2006 at 01:54:39AM +0100, Francois Romieu wrote:
> > No, that wouldn't make sense, that's like making a workaround depend on
> > arch == i386.
> >
> > I'm thinking that we should somehow enable this option on the n2100
> > built-in r8169 ports by default only. Since the n2100
Alexey Dobriyan wrote:
On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
For what it's worth, I don't see any problem with binary drivers from hardware
manufacturers.
Binary drivers from hardware manufacturers are crap. Learn it by heart.
That's your personal opinion! A lot
On Sat, 16 Dec 2006, Alan wrote:
> > blather and idiotic hogwash. "Information" doesn't want to be free, nor is
> > it somethign you should fight for or necessarily even encourage.
>
> As a pedant that is the one item I have to pick you up on Linus.
> Information wants to be free, the natural
On Fri, 15 Dec 2006 16:37:15 -0500, Dave Jones <[EMAIL PROTECTED]> wrote:
> Linux version 2.6.18-1.2864.fc6 ([EMAIL PROTECTED]) (gcc version 4.1.1
> 20061011 (Red Hat 4.1.1-30)) #1 SMP Fri Dec 15 13:14:58 EST 2006
> Kernel command line: ro root=/dev/VolGroup00/LogVol00 profile=1 vga=791
>
isicom, fix locking in isr
2 spin_unlocks are omitted in the interrupt handler. Put them there to fix
up deadlocking on UP.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit f2d37e8d3de070f8cda48a454f7b991d29b310be
tree 23027dcdc3215fbb488577edb9610322956edb0b
parent
isicom, augment card_reset
- add 0xee to signatures
- change long delays to sleeps
- make one sleep shorter not to wait 3s
- portcount == 16 is also correct
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 405c17b09b010b41f6ec2388a11777e4048c7976
tree
isicom, check card state in isr
Check if the card really interrupted us by reading its IO space and
eventualy return IRQ_NONE.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 601667e4ee38183358ea8f7980537bb8c09d8728
tree ccb1c085309ad35178f8d741e7c074308ae277ee
parent
isicom, fix probe race
Fix two race conditions in the probe function with mutex.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit e7087b32ad4b5ee1240fa7f9ba46a9b4566fe424
tree 28bc5ad2a47c03e1b7a09fce22afbe7000955e97
parent f2d37e8d3de070f8cda48a454f7b991d29b310be
author Jiri Slaby
isicom, support higher rates
Add support for higher baud rates (coming from original isi driver).
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 8b380d8b1c3ff7d09d68d467d2f135774cab4086
tree d1e9332d7dc76c5f1d80f936bca71312d0bcb07b
parent 601667e4ee38183358ea8f7980537bb8c09d8728
> >The idea behind the cloneset is that most of the blocks (or files)
> >do not change in either source or target. This being the case its only
> necessary
> >to update the changed elements. This means updates are incremental. Once
> >the system has figured out what it needs to update its usable
> blather and idiotic hogwash. "Information" doesn't want to be free, nor is
> it somethign you should fight for or necessarily even encourage.
As a pedant that is the one item I have to pick you up on Linus.
Information wants to be free, the natural efficient economic state of
information is
> Plus compile error. It should be some search I should do, but
> which one?
>
> drivers/video/sa1100fb.c:1447:49: macro "INIT_WORK" passed 3
> arguments, but takes just 2
> drivers/video/sa1100fb.c: In function `sa1100fb_init_fbinfo':
> drivers/video/sa1100fb.c:1447: error: `INIT_WORK'
On Sat, Dec 16, 2006 at 12:58:18AM +0100, Pavel Machek wrote:
> Hi!
>
> I get nasty warning for each file compiled:
>
> CC drivers/video/sa1100fb.o
> In file included from include/asm/bitops.h:23,
> from include/linux/bitops.h:9,
> from
> > We have designed a new stackable file system that we called RAIF:
> > Redundant Array of Independent Filesystems.
> >
> > Similar to Unionfs, RAIF is a fan-out file system and can be mounted over
> > many different disk-based, memory, network, and distributed file systems.
> > RAIF can use the
Lennert Buytenhek <[EMAIL PROTECTED]> :
[...]
> No, that wouldn't make sense, that's like making a workaround depend on
> arch == i386.
>
> I'm thinking that we should somehow enable this option on the n2100
> built-in r8169 ports by default only. Since the n2100 also has a mini-PCI
> slot, and
The line discipline code numbers N_* are currently defined
separately for each architecture in include/asm-${arch}/termios.h
which is in turn included by include/linux/termios.h via the
symlink include/asm. I don't see any reason why these definitions
need to be architecture specific. They are
On Sat, 16 Dec 2006, karderio wrote:
>
> If the "free software community" has the clout to twist vendor's arms to
> get them release driver source, then I'm all for it.
I don't care what you're for, or what your imaginary "free software
community" is for.
We're "open source", and we're not a
On Wed, 13 Dec 2006, Nikolai Joukov wrote:
We have designed a new stackable file system that we called RAIF:
Redundant Array of Independent Filesystems.
Similar to Unionfs, RAIF is a fan-out file system and can be mounted over
many different disk-based, memory, network, and distributed file
On Sat, 16 Dec 2006 00:25:43 +0059
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > Temporarily at
> >
> > http://userweb.kernel.org/~akpm/2.6.20-rc1-mm1/
> >
> > Will appear later at
> >
> >
> >
[EMAIL PROTECTED]:~$ uname -r
2.6.19.1-rt15_00
And I'm totally thrilled since this is the first -rt kernel that I've
tried and been able to boot since .16-rt29. Yay!
[EMAIL PROTECTED]:~$ zcat /proc/config.gz | egrep "HZ.*=y"
CONFIG_HZ_1000=y
100 revs; min: 5008 max: 5034 avg: 5015
100 revs;
On Thu, Dec 14, 2006 at 10:59:13PM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.19-mm1:
>...
> +debugging-feature-proc-timer_list.patch
>
> Refreshed, refactored dynticks/hrtimer queue.
>...
I'd assume sysrq_timer_list_show() wasn't intended to be unused?
cu
Adrian
--
"Is
On Fri, 15 Dec 2006 11:24:12 -0800, Andrew Morton wrote:
>On Fri, 15 Dec 2006 15:45:55 +0059
>Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> Andrew Morton wrote:
>> > Temporarily at
>> >
>> >http://userweb.kernel.org/~akpm/2.6.20-rc1-mm1/
>> >
>> > Will appear later at
>> >
>> >
>> >
Hi!
I get nasty warning for each file compiled:
CC drivers/video/sa1100fb.o
In file included from include/asm/bitops.h:23,
from include/linux/bitops.h:9,
from include/linux/thread_info.h:20,
from include/linux/preempt.h:9,
On Friday 15 December 2006 15:11, Nikolai Joukov wrote:
> > On Wednesday 13 December 2006 12:47, Nikolai Joukov wrote:
> > > We have designed a new stackable file system that we called RAIF:
> > > Redundant Array of Independent Filesystems
> >
> > Do you have a function similar to an an EMC
Hi :o)
Linus Torvalds wrote :
> The silly thing is, the people who tend to push most for this are the
> exact SAME people who say that the RIAA etc should not be able to tell
> people what to do with the music copyrights that they own, and that the
> DMCA is bad because it puts technical
Mikael Pettersson wrote:
> Applying the trivial patch below on top of 2.6.20-rc1-mm1 should
Yup, Jeff fwd me this yet and it works.
thanks,
--
http://www.fi.muni.cz/~xslaby/Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey
On 12/15/06, Jarek Poplawski <[EMAIL PROTECTED]> wrote:
On 12-12-2006 20:49, Alessandro Suardi wrote:
> Very shortly after boot on my K7-800 running up-to-date FC6
> and 2.6.19-git19; didn't happen in 2.6.19-vanilla:
...
> [ 134.915521] INFO: trying to register non-static key.
> [ 134.915890]
http://www.minix3.org/
maybe this development will spur an open device driver standard, or adoption
of wrappers for the unified BSD driver standard into other frameworks
--
He thought he could organize freedom
how naive and controlling of him
-
To unsubscribe from this list: send the line
On Friday, 15 December 2006 23:24, Jeff Garzik wrote:
> Rafael J. Wysocki wrote:
> > On Friday, 15 December 2006 22:39, Andrew Morton wrote:
> >> On Fri, 15 Dec 2006 13:05:52 -0800
> >> Andrew Morton <[EMAIL PROTECTED]> wrote:
> >>
> >>> Jeff, I shall send all the sata patches which I have at you
Andrew Morton wrote:
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-rc1-mm1/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc1/2.6.20-rc1-mm1/
Ok, after fixing sata_promise, I got this 7 times:
[ 30.957539]
On Fri, 15 Dec 2006, Robert P. J. Day wrote:
> On Fri, 15 Dec 2006, Jan Engelhardt wrote:
> > Even sizeof a / sizeof *a
> >
> > may happen.
>
> yes, sadly, there are a number of those as well. back to the drawing
> board.
It might be interesting to grep for anything that divides two sizeofs
On Fri, 2006-12-15 at 09:34 +0100, Christoph Hellwig wrote:
> On Thu, Dec 14, 2006 at 04:07:55PM -0800, Matt Helsley wrote:
> > Associate function calls with significant events in a task's lifetime much
> > like
> > we handle kernel and module init/exit functions. This creates a table for
> >
Hello Mark,
On Thu, Dec 14, 2006 at 03:20:24PM -0500, Mark Drago wrote:
> Hello,
>
> I have been seeing some kernel panics on a Dell PowerEdge 2650 with a
> PERC 3/Di raid controller doing RAID 1. I have now seen the panics
> occur on multiple PE2650s. The panic seems to occur during periods
On Wed, 13 Dec 2006, Nick Piggin wrote:
> Linus Torvalds wrote:
> >
> > On Tue, 12 Dec 2006, Russell King wrote:
> > >
> > > Why can't we just use atomic_t for this?
> >
> >
> > Well, others have answered that ("wrong sizes"), but I'm wavering on using
> > atomic_long_t. I have to admit that
Andrew Morton wrote:
> On Fri, 15 Dec 2006 15:45:55 +0059
> Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> Andrew Morton wrote:
>>> Temporarily at
>>>
>>> http://userweb.kernel.org/~akpm/2.6.20-rc1-mm1/
>>>
>>> Will appear later at
>>>
>>>
>>>
So I'm trying to get an understanding of the interactions between the
various aio_read/aio_write paths, and I ran across this gem at the end
of generic_file_buffered_write:
/*
* For now, when the user asks for O_SYNC, we'll actually give O_DSYNC
*/
if (likely(status
On Friday, 15 December 2006 23:19, Jeff Garzik wrote:
> Alan wrote:
> > On Fri, 15 Dec 2006 13:39:27 -0800
> > Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> >> On Fri, 15 Dec 2006 13:05:52 -0800
> >> Andrew Morton <[EMAIL PROTECTED]> wrote:
> >>
> >>> Jeff, I shall send all the sata patches
Rafael J. Wysocki wrote:
On Friday, 15 December 2006 22:39, Andrew Morton wrote:
On Fri, 15 Dec 2006 13:05:52 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
Jeff, I shall send all the sata patches which I have at you one single time
and I shall then drop the lot. So please don't flub them.
On Friday, 15 December 2006 22:39, Andrew Morton wrote:
> On Fri, 15 Dec 2006 13:05:52 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Jeff, I shall send all the sata patches which I have at you one single time
> > and I shall then drop the lot. So please don't flub them.
> >
> > I'll
Alan wrote:
On Fri, 15 Dec 2006 13:39:27 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
On Fri, 15 Dec 2006 13:05:52 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
Jeff, I shall send all the sata patches which I have at you one single time
and I shall then drop the lot. So please don't flub
On Fri, 2006-12-15 at 09:34 +0100, Christoph Hellwig wrote:
> On Thu, Dec 14, 2006 at 04:07:55PM -0800, Matt Helsley wrote:
> > Associate function calls with significant events in a task's lifetime much
> > like
> > we handle kernel and module init/exit functions. This creates a table for
> >
On 2006/12/15 at 15:44:14 Trond Myklebust <[EMAIL PROTECTED]> wrote
> On Fri, 2006-12-15 at 15:06 -0600, Michal Sabala wrote:
> > Could this be related to the fact that the nfs mmaped file is unlinked
> > before it is ummaped? The .nfsXXX file disappears from the NFS
> > server as soon as
On Dec 15 2006 21:27, Jörn Engel wrote:
>On Fri, 15 December 2006 22:01:10 +0100, Jan Engelhardt wrote:
>> On Dec 15 2006 15:56, Dmitry Torokhov wrote:
>> >
>> > outside the loop? If not then it is better to keep style consistent
>> > and not use condensed form in loops either.
>>
>> Don't you
On Fri, Dec 15, 2006 at 09:20:58PM +, James Porter wrote:
> I think some kernel developers take to much responsibility, is there a bug in
> a
> binary driver? Send it upstream and explain to the user that it's a closed
> source driver and is up to said company to fix it.
>
> For what it's
On Dec 15 2006 21:59, Alan wrote:
>
>> I personally like nvidia's products, they have spent a lot of money in R
>> One
>> example is SLI, if their spec was open what would stop ATI from stealing
>> their
>
>3DFx invented SLI many years ago. The SLI programming information for the
>3DFx cards is
On Friday, 15 December 2006 23:06, Alan wrote:
> On Fri, 15 Dec 2006 13:39:27 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 15 Dec 2006 13:05:52 -0800
> > Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > Jeff, I shall send all the sata patches which I have at you one single
>
On Fri, 15 Dec 2006 13:39:27 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 15 Dec 2006 13:05:52 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Jeff, I shall send all the sata patches which I have at you one single time
> > and I shall then drop the lot. So please don't flub
On Friday, 15 December 2006 22:49, Jeff Garzik wrote:
> Rafael J. Wysocki wrote:
> > The other box is mine and it works just fine with 2.6.20-rc1.
> >
> >> I think something bad happened in sata land just recently.
> >
> > Yup. Please see, for example:
> >
> >
The "Re: Linux 2.6.20-rc1" sub-thread that had Jens and Alistair John
Strachan replying seemed to implicate some core block layer badness.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Rafael J. Wysocki wrote:
The other box is mine and it works just fine with 2.6.20-rc1.
I think something bad happened in sata land just recently.
Yup. Please see, for example:
http://marc.theaimsgroup.com/?l=linux-kernel=116621656432500=2
It looks like the breakage is in sata, in the
> I personally like nvidia's products, they have spent a lot of money in R
> One
> example is SLI, if their spec was open what would stop ATI from stealing their
3DFx invented SLI many years ago. The SLI programming information for the
3DFx cards is public. Nvidia are a bit late to the party
On Friday, 15 December 2006 22:39, Andrew Morton wrote:
> On Fri, 15 Dec 2006 13:05:52 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Jeff, I shall send all the sata patches which I have at you one single time
> > and I shall then drop the lot. So please don't flub them.
> >
> > I'll
On Fri, 2006-12-15 at 15:06 -0600, Michal Sabala wrote:
> On 2006/12/15 at 13:44:44 Trond Myklebust <[EMAIL PROTECTED]> wrote
> > On Fri, 2006-12-15 at 11:50 -0600, Michal Sabala wrote:
> > > On 2006/12/15 at 10:24:15 Trond Myklebust <[EMAIL PROTECTED]> wrote
> > > > On Thu, 2006-12-14 at 20:30
On 2006/12/15 at 15:12:06 Arjan van de Ven <[EMAIL PROTECTED]> wrote
>
> >
> > I do not have any indication that it is the server not responding. Other
> > applications which have NFS files open are continuing to work while in
> > this case XFree86 blocks.
>
> just a strange question, but which
On Fri, 15 Dec 2006 15:35:00 -0600
Michal Sabala <[EMAIL PROTECTED]> wrote:
> On 2006/12/15 at 14:42:08 Andrew Morton <[EMAIL PROTECTED]> wrote
> > On Fri, 15 Dec 2006 11:50:30 -0600
> > Michal Sabala <[EMAIL PROTECTED]> wrote:
> >
> > > On 2006/12/15 at 10:24:15 Trond Myklebust <[EMAIL
On Fri, 15 Dec 2006 13:05:52 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Jeff, I shall send all the sata patches which I have at you one single time
> and I shall then drop the lot. So please don't flub them.
>
> I'll then do a rc1-mm2 without them.
hm, this is looking like a lot of work
On Fri, Dec 15, 2006 at 09:53:44AM -0800, Greg Kroah-Hartman wrote:
> On Fri, Dec 15, 2006 at 12:50:27PM -0500, Dave Jones wrote:
> > Happens during every boot, though bootup continues afterwards.
>
> Can you enable CONFIG_USB_DEBUG and send the log info that happens right
> before this
On Fri, Dec 15, 2006 at 09:53:44AM -0800, Greg Kroah-Hartman wrote:
> On Fri, Dec 15, 2006 at 12:50:27PM -0500, Dave Jones wrote:
> > Happens during every boot, though bootup continues afterwards.
>
> Can you enable CONFIG_USB_DEBUG and send the log info that happens right
> before this
On 2006/12/15 at 14:42:08 Andrew Morton <[EMAIL PROTECTED]> wrote
> On Fri, 15 Dec 2006 11:50:30 -0600
> Michal Sabala <[EMAIL PROTECTED]> wrote:
>
> > On 2006/12/15 at 10:24:15 Trond Myklebust <[EMAIL PROTECTED]> wrote
> > > On Thu, 2006-12-14 at 20:30 -0600, Michal Sabala wrote:
> > > >
> > >
On Fri, 15 December 2006 22:01:10 +0100, Jan Engelhardt wrote:
> On Dec 15 2006 15:56, Dmitry Torokhov wrote:
> >
> > Would you write:
> >
> > i+=2;
> >
> > outside the loop? If not then it is better to keep style consistent
> > and not use condensed form in loops either.
>
> Don't you all
I think some kernel developers take to much responsibility, is there a bug in a
binary driver? Send it upstream and explain to the user that it's a closed
source driver and is up to said company to fix it.
For what it's worth, I don't see any problem with binary drivers from hardware
Jörn Engel wrote:
On Fri, 15 December 2006 21:10:14 +, Jörn Engel wrote:
Like so? I manually edited the patch and weakened a few of the space
rules, basically the ones in dispute in this thread.
Btw, this doesn't apply to my git tree at all (just pulled):
Hunk #1 FAILED at 35.
Hunk #2
Patch 2 of 2
This patch fixes a stupid bug. Sometime during the 2tb enhancement I ended up
replacing the macros XFER_READ and XFER_WRITE with h->cciss_read and
h->cciss_write respectively. It seemed to work somehow at least on x86_64 and
ia64. I don't know how. But people started complaining
> +static int pgm_check_occured;
> +
> +static void cio_reset_pgm_check_handler(void)
> +{
> + pgm_check_occured = 1;
> +}
> +
> +static int stsch_reset(struct subchannel_id schid, volatile struct schib
> *addr)
> +{
> + int rc;
> +
> + pgm_check_occured = 0;
> +
I don't think it's in -rc1, please see below.
On Friday, 15 December 2006 21:50, Neil Brown wrote:
> On Friday December 15, [EMAIL PROTECTED] wrote:
> > From: Neil Brown <[EMAIL PROTECTED]>
> > Date: Wed, Dec 06, 2006 at 06:20:57PM +1100
> > > i.e. current -mm is good for 2.6.20 (though I have a
On Fri, 15 December 2006 12:26:59 -0800, Randy Dunlap wrote:
>
> then send patches :)
Like so? I manually edited the patch and weakened a few of the space
rules, basically the ones in dispute in this thread.
From: Randy Dunlap <[EMAIL PROTECTED]>
Add some kernel coding style comments, mostly
On Fri, 15 December 2006 21:10:14 +, Jörn Engel wrote:
>
> Like so? I manually edited the patch and weakened a few of the space
> rules, basically the ones in dispute in this thread.
Btw, this doesn't apply to my git tree at all (just pulled):
Hunk #1 FAILED at 35.
Hunk #2 FAILED at 94.
On Fri, Dec 15, 2006 at 10:03:29PM +0100, Lennert Buytenhek wrote:
> On Fri, Dec 15, 2006 at 09:15:22PM +0100, Francois Romieu wrote:
>
> > > Is there a way we can have this done by default on the n2100? I guess
> > > that since it's a PCI device, there isn't much hope for that..?
> >
> > Do
On Friday, 15 December 2006 22:05, Andrew Morton wrote:
> On Sat, 16 Dec 2006 07:50:01 +1100
> Neil Brown <[EMAIL PROTECTED]> wrote:
>
> > On Friday December 15, [EMAIL PROTECTED] wrote:
> > > From: Neil Brown <[EMAIL PROTECTED]>
> > > Date: Wed, Dec 06, 2006 at 06:20:57PM +1100
> > > > i.e.
>
> I do not have any indication that it is the server not responding. Other
> applications which have NFS files open are continuing to work while in
> this case XFree86 blocks.
just a strange question, but which video driver do you use in X? maybe
that one is blocking say the pci bus or
On 2006/12/15 at 13:44:44 Trond Myklebust <[EMAIL PROTECTED]> wrote
> On Fri, 2006-12-15 at 11:50 -0600, Michal Sabala wrote:
> > On 2006/12/15 at 10:24:15 Trond Myklebust <[EMAIL PROTECTED]> wrote
> > > On Thu, 2006-12-14 at 20:30 -0600, Michal Sabala wrote:
> > > >
> > > > `cat
PATCH 1 of 2
This patch sets a default raid level on a volume that either does not support
reading the geometry or reports an invalid geometry for whatever reason. We
were always setting some values for heads and sectors but never set a raid
level. This caused lots of problems on some buggy
On Dec 15 2006 15:56, Dmitry Torokhov wrote:
> On 12/15/06, Jörn Engel <[EMAIL PROTECTED]> wrote:
>> On Fri, 15 December 2006 09:00:37 -0800, Randy Dunlap wrote:
>> > On Fri, 15 Dec 2006 16:07:17 +0100 Pavel Machek wrote:
>> >
>> > > Not in simple cases.
>> > >
>> > > 3*i + 2*j should be writen
On Sat, 16 Dec 2006 07:50:01 +1100
Neil Brown <[EMAIL PROTECTED]> wrote:
> On Friday December 15, [EMAIL PROTECTED] wrote:
> > From: Neil Brown <[EMAIL PROTECTED]>
> > Date: Wed, Dec 06, 2006 at 06:20:57PM +1100
> > > i.e. current -mm is good for 2.6.20 (though I have a few other little
> > >
On Fri, 15 Dec 2006 21:39:36 +0100
Damien Wyart <[EMAIL PROTECTED]> wrote:
> With this new kernel, I notice two messages I do not have with
> 2.6.19-rc6-mm2 :
>
> Dec 15 20:00:47 brouette kernel: Filesystem "sdb9": Disabling barriers,trial
> barrier write failed
> Dec 15 20:00:47 brouette
On Fri, Dec 15, 2006 at 09:15:22PM +0100, Francois Romieu wrote:
> > Is there a way we can have this done by default on the n2100? I guess
> > that since it's a PCI device, there isn't much hope for that..?
>
> Do you mean an automagically tuned default value based on CONFIG_ARM ?
No, that
Hi again,
As a companion to today's libsas roll-up, this is the queue of patches
for the SATL connector between SAS and ATA. For patches not
specifically focusing on SAS ATA, please refer to my previous email (or
the patches themselves). Each patch has its own preamble description,
but I'd like
On Fri, 15 Dec 2006 16:13:28 +0300
Vitaly Wool <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> the trivial patch below fixes the compilation failure for smc911x.c when
> NET_POLL_CONTROLLER is set.
>
> drivers/net/smc911x.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
On 12/15/06, Jörn Engel <[EMAIL PROTECTED]> wrote:
On Fri, 15 December 2006 09:00:37 -0800, Randy Dunlap wrote:
> On Fri, 15 Dec 2006 16:07:17 +0100 Pavel Machek wrote:
>
> > Not in simple cases.
> >
> > 3*i + 2*j should be writen like that. Not like
> > (3 * i) + (2 * j)
>
> I would
1 - 100 of 493 matches
Mail list logo
