[EMAIL PROTECTED] wrote:
>
> Patch 3 of 8
> This patch removes a couple of functions dealing with configuration and
> replaces them with new functions. This implementation fixes some bugs
> associated with the ACUXE. It also allows a logical volume to be removed
> from the middle without deleting
On Fri, 9 Sep 2005 17:44:03 -0700 (PDT) Paul Jackson wrote:
> Code reading uncovered a potential deadlock on the global cpuset
> semaphore, cpuset_sem.
>
> ==> This patch is only useful in the 2.6.13-stable series.
Paul,
stable patch candidates should be sent to [EMAIL PROTECTED]
Chris/Greg,
m
> Date: Fri, 9 Sep 2005 11:33:52 +0100 (BST)
> From: Mark Underwood <[EMAIL PROTECTED]>
>
> ...
> > That implies whoever is registering is actually
> > going and creating the
> > SPI devices ... and doing it AFTER the controller
> > driver is registered.
> > I actually have issues with each of thos
On 9/9/05, Anthony Wesley <[EMAIL PROTECTED]> wrote:
> Okay, just tested a couple of things, here's what I see...
>
> I tested the write speed to the usb2 hard disk and got 21MBytes/sec. It's a
> laptop
> hard drive, only 5400rpm so this is not surprising.
>
> I did this test with my video captu
On Fri, 10 Sep 2005, Andi Kleen wrote:
> On Fri, Sep 09, 2005 at 10:07:28AM -0700, Zwane Mwaikambo wrote:
> > On Tue, 6 Sep 2005, Ashok Raj wrote:
> >
> > > On Tue, Sep 06, 2005 at 01:16:28AM +0200, Andi Kleen wrote:
> > > > On Sat, Sep 03, 2005 at 02:33:30PM -0700, [EMAIL PROTECTED] wrote:
> > >
Hi,
On Fri, 9 Sep 2005, john stultz wrote:
> +/* Required to safely shift negative values */
> +#define shiftR(x, s) ({ __typeof__(x) __x = x;\
> + __typeof__(s) __s = s; \
> + (__x < 0) ? (-((-__x) >> (__s))) : ((__x) >> (__s));})
> +
Some parenthesis are missing and som
Linus Torvalds wrote:
On Fri, 9 Sep 2005, Andrew Morton wrote:
If something like a PCI power management function fails then it will likely
cause suspend or resume to malfunction, and we have a lot of such problems.
No, for several reasons.
First off, some of those functions can't fail in n
Nishanth Aravamudan <[EMAIL PROTECTED]> wrote:
>
> Description: The current sys_poll() implementation does not seem to
> handle large timeouts correctly. Any value in milliseconds (@timeout)
> which exceeds the maximum representable jiffy value
> (MAX_SCHEDULE_TIMEOUT) should result in a MAX_SCH
> cpuset-semaphore-depth-check-deadlock-fix-rename.patch
Acked-by: Paul Jackson <[EMAIL PROTECTED]>
(thanks, Andrew)
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To un
In article <[EMAIL PROTECTED]> (at Fri, 09 Sep 2005 18:03:37 -0700), john
stultz <[EMAIL PROTECTED]> says:
> diff --git a/kernel/time.c b/kernel/time.c
> --- a/kernel/time.c
> +++ b/kernel/time.c
> @@ -338,30 +338,20 @@ int do_adjtimex(struct timex *txc)
> if (mtemp >= MINSE
All,
Here is hopefully a fairly uncontroversial cleanup for the NTP code. It
uses min/max to simplify some conditionals and creates a macro shiftR
that avoids the numerous ugly conditionals in the NTP code that look
like:
if(a < 0)
b = -(-a >> shift);
Okay, just tested a couple of things, here's what I see...
I tested the write speed to the usb2 hard disk and got 21MBytes/sec. It's a laptop
hard drive, only 5400rpm so this is not surprising.
I did this test with my video capture app running, but just displaying data and
not writing,
I hav
Based on a better understanding of dirty_ratio and dirty_background ratio
(thanks Nate) I just tried
the following test:
dirty_ratio set to 95
dirty_background_ratio set to 1
From Nate's description of these parameters, this should mean that the disk
writes
start almost immediately, and the
Code reading uncovered a potential deadlock on the global cpuset
semaphore, cpuset_sem.
==> This patch is only useful in the 2.6.13-stable series.
(It's harmless, and useless, in the pre 2.6.14 fork)
The pre-2.6.14 fork has already diverged, with an additional patch
that further aggrevated t
On 9/9/05, Anthony Wesley <[EMAIL PROTECTED]> wrote:
> Hi Nate and Roger,
>
> First off, thanks fo taking some time to answer my call for help :-)
>
> I've already spent some time fiddling with dirty_ratio before I posted my
> question - yes, I can make different things happen by increasing or
>
On 06.09.2005 [14:25:14 -0700], Nishanth Aravamudan wrote:
> On 31.08.2005 [13:01:09 -0700], Nishanth Aravamudan wrote:
> > Sorry everybody, forgot the most important Cc: :)
> >
> > -Nish
> >
> > Hi Andrew,
> >
> > In looking at Bug 5132 and sys_poll(), I think there is a flaw in the
> > current
On Fri, Sep 09, 2005 at 10:07:28AM -0700, Zwane Mwaikambo wrote:
> On Tue, 6 Sep 2005, Ashok Raj wrote:
>
> > On Tue, Sep 06, 2005 at 01:16:28AM +0200, Andi Kleen wrote:
> > > On Sat, Sep 03, 2005 at 02:33:30PM -0700, [EMAIL PROTECTED] wrote:
> > > >
> > > > From: Ashok Raj <[EMAIL PROTECTED]>
>
On Fri, 9 Sep 2005, Andrew Morton wrote:
>
> If something like a PCI power management function fails then it will likely
> cause suspend or resume to malfunction, and we have a lot of such problems.
No, for several reasons.
First off, some of those functions can't fail in normal usage. Thus
t
This is the second part, with some example code for each part
of the system an SPI stack would need to provide.
- Dave
-- SNIP!
This has code for two SPI examples:
- "ads7846.c" -- a protocol driver that reads some sensors.
- "spi_plat_example.c" sets up up a m
On Friday 09 September 2005 19:50, Chuck Ebbert wrote:
> In-Reply-To: <[EMAIL PROTECTED]>
>
> On Fri, 9 Sep 2005 at 12:14:38 +0100 (BST), Hugh Dickins wrote:
> > On Fri, 9 Sep 2005, Andi Kleen wrote:
> > > It won't give more accurate backtraces, not even on i386 because
> > > show_stack doesn't hav
Hi Nate and Roger,
First off, thanks fo taking some time to answer my call for help :-)
I've already spent some time fiddling with dirty_ratio before I posted my
question - yes, I can make different things happen by increasing or decreasing
it, but overall I still have the same problem - my vi
> > This is what my SPI core tries to do. I would like to
> > make at 'as small as possible and no smaller'
>
> I'll post a refresh of my patch that seems to me to be
> a much better match for those goals. The refresh includes
> some tweaks based on what you sent, but it's still just
> one KByte o
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
>
> On Fri, 9 Sep 2005, Greg KH wrote:
> >
> > I fixed up all of the PCI core and USB drivers that were flagged by
> > these warnings already. Biggest area left is network drivers that I
> > saw.
>
> The reason I really dislike patches like these i
processor_idle.c vs Lindent resulted in something of a trainwreck
with inconsistent whitespace. This diff rearranges the
processor_power_dmi_table to look like it did before that accident,
and adds two additional BIOS's to the list as encountered by
Fedora users.
https://bugzilla.redhat.com/bugzi
On Fri, 2005-09-09 at 15:42 -0400, Luben Tuikov wrote:
> +static const struct scsi_host_template sas_host_template = {
> + .module = THIS_MODULE,
> + /* .name is initialized */
> + .name = "",
> + .queuecommand = sas_queuecommand,
> + .eh_strategy_handler = sas_scsi_re
Linus wrote:
> We _really_ don't want to have function names like "cs_up()"
I thoroughly agree with your attention to naming, and spent more time
than I will admit in public futzing over this detail.
I wrote the code using cpuset_lock(void) and cpuset_unlock(void), for
reasons such as you state,
On Fri, 9 Sep 2005, Linus Torvalds wrote:
>
> There are functions where it is really _important_ to check the error
> return, because they return errors often enough - and the error case is
> something you have to do something about - that it's good to force people
> to be aware.
>
> But "pc
On Fri, 2005-09-09 at 15:40 -0400, Luben Tuikov wrote:
> +/**
> + * sas_do_lu_discovery -- Discover LUs of a SCSI device
> + * @dev: pointer to a domain device of interest
Aside from all the other problems, this one completely duplicates the
mid-layer infrastructure for handling devices with Logic
On Fri, 9 Sep 2005, Greg KH wrote:
>
> I fixed up all of the PCI core and USB drivers that were flagged by
> these warnings already. Biggest area left is network drivers that I
> saw.
The reason I really dislike patches like these is that it causes people to
do questionable things.
For examp
On Fri, Sep 09, 2005 at 03:37:16PM -0700, Linus Torvalds wrote:
>
>
> On Fri, 9 Sep 2005, Greg KH wrote:
> >
> > Dave Jones:
> > must_check attributes for PCI layer.
>
> Why?
This is something that David and Arjan wanted in. Guys?
> This only clutters up the compile, hiding real errors.
>
Deleted obsolete stuff from arch makefile
Renamed .c file to asm-offsets.h
Fix include of asm-offsets.h to use new name
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/v850/Makefile | 14 +
arch/v850/kernel/asm-consts.c | 61
Signed-off-by: Luben Tuikov <[EMAIL PROTECTED]>
diff -X linux-2.6.13-mm2/Documentation/dontdiff -Naur
linux-2.6.13-mm2-orig/include/scsi/sas/sas.h
linux-2.6.13-mm2/include/scsi/sas/sas.h
--- linux-2.6.13-mm2-orig/include/scsi/sas/sas.h1969-12-31
19:00:00.0 -0500
+++ linux-2.6.13
Delete obsoleted parts form arch makefiles and rename to asm-offsets.h
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/m68k/Makefile |9 -
arch/m68k/fpsp040/skeleton.S|2 +-
arch/m68k/ifpsp060/iskeleton.S |2 +-
arch/m68k/ke
Delete obsolete stuff from arch Makefile
Rename file to asm-offsets.h
The trick used in the arch Makefile to circumvent the circular
dependency is kept.
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/ia64/Makefile | 21 +++--
arch/ia64/ia32/ia32_entry.S |
Removed obsolete stuff from arch makefile.
mips had a special rule for generating asm-offsets.h so preserved it
using an architecture specific hook in top-level Kbuild file.
Renamed .h file to asm-offsets.h
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
Kbuild |
um has it own set of files for asm-offsets. So for now the
gen-asm-offset macro is just duplicated in the um Makefile.
This may well be the final solution since um is a bit special compared
to other architectures - time will tell.
Also added a dummy arch/um/kernel/asm-offsets.h file to keep kbuil
Cris has a dedicated asm-offsets.c file per subarchitecture.
So a symlink is created to put the desired asm-offsets.c file
in $(ARCH)/kernel
This is absolutely not good practice, but it was the trick
used in the rest of the cris code.
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/cri
Delete obsolete stuff from arch makefiles
Rename .h file to asm-offsets.h
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/alpha/Makefile | 11 ---
arch/alpha/kernel/entry.S|2 +-
arch/alpha/kernel/head.S |2 +-
arch/alpha/lib/d
Needed to get them to build.
And a hint to avoid hardcoding to many constants in assembler.
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/frv/kernel/asm-offsets.c |1 +
arch/m32r/kernel/asm-offsets.c|1 +
arch/sparc64/kernel/asm-offsets.c |1 +
3 files changed, 3
Delete obsoleted stuff from arch Makefile and rename
constants.h to asm-offsets.h
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/arm/Makefile |9 ++---
arch/arm/kernel/entry-header.S |2 +-
arch/arm/kernel/head.S |2 +-
arch/arm/kernel/
[Seems that first attempt sending out this patchset went wrong..]
The following 12 patches introduces full dependency tracking on the
generated asm-offsets.h file.
It also consolidate the rules required to build the asm-offsets.h file
in a new file named Kbuild in the top-level directory.
Introdu
Rename all includes to use asm-offsets.h to match generic name
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/arm26/Makefile | 10 --
arch/arm26/kernel/entry.S|2 +-
arch/arm26/lib/copy_page.S |2 +-
arch/arm26/lib/csumpartialco
Building asm-offsets.h has been moved to a seperate Kbuild file
located in the top-level directory. This allow us to share the
functionality across the architectures.
The old rules in architecture specific Makefiles will die
in subsequent patches.
Furhtermore the usual kbuild dependency tracking
h8300, m68knommu, sh and sh64 all used the name asm-offsets.h so minimal
changes required.
Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]>
---
arch/h8300/Makefile |8
arch/m68knommu/Makefile | 10 --
arch/sh/Makefile| 11 ++-
arch/sh64/Makefile
Andrew,
The following is a patchset of the SAS code as posted
today but it has the suggestions by Nish and Alexey,
and it is against -mm2 tree.
Signed-off-by: Luben Tuikov <[EMAIL PROTECTED]>
diff -X linux-2.6.13-mm2/Documentation/dontdiff -Nau
linux-2.6.13-mm2-orig/drivers/scsi/Kconfig linux-2
On Fri, 9 Sep 2005, Greg KH wrote:
>
> Dave Jones:
> must_check attributes for PCI layer.
Why?
This only clutters up the compile, hiding real errors.
I think all those compile warnings are totally bogus. Who really cares?
Are they going to be fixed, or were they added just to irritate peop
On Fri, 2005-09-09 at 13:12 +0900, Magnus Damm wrote:
> On 9/9/05, KUROSAWA Takahiro <[EMAIL PROTECTED]> wrote:
> > On Thu, 8 Sep 2005 05:02:32 -0700
> > Paul Jackson <[EMAIL PROTECTED]> wrote:
> > > One of my passions is to avoid special cases across API boundaries.
> > >
> > > I am proposing that
On 08.09.2005 [15:08:54 -0700], Nishanth Aravamudan wrote:
> On 08.09.2005 [14:22:13 -0700], Nishanth Aravamudan wrote:
> > On 08.09.2005 [13:00:36 +0300], Tony Lindgren wrote:
> > > * Nishanth Aravamudan <[EMAIL PROTECTED]> [050907 18:07]:
> > > > On 07.09.2005 [10:37:43 +0300], Tony Lindgren wrot
Alon Bar-Lev wrote:
I see it as a good thing it hasen't ben included in the kernel tree
-
Strange...
Since documentation available in site and in
Documentation/power/suspend2.txt.
And that many people with laptops uses it...
But everyone with his problems :)
Alon.
all of that assumes
Those files live in include/scsi/sas/ and were missed in the
previous patchset:
sas.h
sas_class.h
sas_discover.h
sas_expander.h
sas_frames.h
sas_frames_be.h
sas_frames_le.h
sas_task.h
Signed-off-by: Luben Tuikov <[EMAIL PROTECTED]>
diff -X linux-2.6.13/Documentation/dontdiff -Naur
linux-2.6.13-
On Sat, Sep 10, 2005 at 01:58:14AM +0400, Evgeniy Polyakov wrote:
> I'm sorry - quite far from testing machines...
> Here is additional patch for ds_2433.c - it adds two missing defines.
>
> --- ./drivers/w1/w1_ds2433.c.orig 2005-09-10 01:59:41.0 +0400
> +++ ./drivers/w1/w1_ds2433.c 2
Bart, any word on this? I know you're busy but it would be much appreciated if
you could comment, even if it is hurling abuse ;)
Thanks.
Daniel Drake wrote:
Hows this? I don't have any hardware with two VIA controllers, however I
have tested this on a pc which has a single vt8233a controller.
On Fri, 2005-09-09 at 15:20 -0400, linux-os (Dick Johnson) wrote:
> Because it's now defunct , a zombie, waiting for somebody to
> reap its return status. You are almost there, you need to issue
> the kernel equivalent of waitpid() (sys_waitpid) to grab that
> status and throw it away. That's what
Patch 8 of 8
Add SCSI host and device info not elsewhere available to /proc/scsi/cciss/*
Namely, connect cciss device instance with scsi host number, and
give scsi host number, bus, target, lun, devicetype, and 8-byte cciss LUNID
for each tapedrive/medium changer attached to a controller
For insta
On Fri, 9 Sep 2005, Paul Jackson wrote:
>
> This patch fixes this deadlock by wrapping the up() and down()
> calls on cpuset_sem in kernel/cpuset.c with code that tracks
> the nesting depth of the current task on that semaphore,
We _really_ don't want to have function names like "cs_up()" and
"c
Hi Greg,
The attached patch was created against 2.6.13-git9.
Please consider it for inclusion.
Thanks,
Linda
Signed-off-by: Linda Xie <[EMAIL PROTECTED]>
--- linux-2.6.13-git9/drivers/pci/hotplug/rpadlpar_sysfs.c 2005-08-28
18:41:01.0 -0500
+++ linux-2.6.13-git9-linda/driver
Patch 7 of 8
This patch adds support for "One Button Disaster Recovery" devices
to the cciss driver. (OBDR devices are tape drives which can
pretend to be cd-rom devices temporarily. Once booted the device
can be reverted to a tape drive and data recovery operations can
be automatically begun.)
T
Patch 2 of 8
This patch adds a flag called busy_initializing. If there are multiple
controllers in a server AND the HP agents are running it's possible
the agents may try to poll a card that is still initializing if the
driver is removed and then added again.
Please consider this for inclusion.
S
Patch 3 of 8
This patch removes a couple of functions dealing with configuration and
replaces them with new functions. This implementation fixes some bugs
associated with the ACUXE. It also allows a logical volume to be removed
from the middle without deleting all volumes behind it.
If a user has
Patch 6 of 8
The CCISS driver seems to loose track of DMA mappings
created by it's fill_cmd() routine. Neither callers of this routine are
extracting the DMA address created in order to do the unmap.
Instead, they simply try to unmap 0x0. It's easy to see this
problem on an x86_64 system when usi
Here are some more PCI patches against your latest git tree. Most of
them were just not applied to the last pci git pull, due to me messing
up the mbox that I applied to the tree. They have been in the -mm tree
for a while.
The other two patches are a moving around of the pci probe functions so
Patch 5 of 8
This patch fixes a bug in cciss_remove_one. A set of braces was missing
for the if statement causing an Oops on driver unload.
Please consider this for inclusion.
Signed-off-by: Mike Miller <[EMAIL PROTECTED]>
cciss.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
-
Patch 4 of 8
This patch changes the way we complete commands. In the old method when we
got a completion we searched our command list from the top until we find it.
This method uses a tag associated with each command (not SCSI command tagging)
to index us directly to the completed command. This hel
Andrew Morton wrote:
>
>
>
>>1. pseudo files or "" files
>>
>>
>>
>
>
>
>> disabled. It remains a point of (extraordinary) contention as to
>>whether it can be fixed, we want to keep the code around until we can
>>devote proper resources into proving it can be (or until we fail to pr
On Fri, Sep 09, 2005 at 02:16:19PM -0700, GregKH ([EMAIL PROTECTED]) wrote:
> On Fri, Sep 09, 2005 at 09:08:25AM +0400, Evgeniy Polyakov wrote:
> > On Thu, Sep 08, 2005 at 08:30:36PM -0700, Greg KH ([EMAIL PROTECTED]) wrote:
> > > On Fri, Sep 09, 2005 at 01:30:09AM +0200, Marcel Holtmann wrote:
> >
The cpusets-formalize-intermediate-gfp_kernel-containment patch
has a deadlock problem.
This patch was part of a set of four patches to make more
extensive use of the cpuset 'mem_exclusive' attribute to
manage kernel GFP_KERNEL memory allocations and to constrain
the out-of-memory (oom) killer.
A
NOTE: All patches in this set have been tested.
Patch 1 of 8
This patch adds new PCI and subsystem ID's that finally made the spec. It also
include a name change for one controller. I know there's a lot of duplicat names
but the fw folks wanted this for the different implementations.
Even though
Hi,
On 09/09/05, Folkert van Heusden <[EMAIL PROTECTED]> wrote:
> Running klive on a sparc.
> Now I wonder: what should/can I run to help by testing a kernel? The sun
> is dedicated for the testing so everything is possible.
>
>
> Folkert van Heusden
>
You have at least 2 ways:
1 - test less b
Here are the same "delete devfs" patches that I submitted for 2.6.12.
It rips out all of devfs from the kernel and ends up saving a lot of
space. Since 2.6.13 came out, I have seen no complaints about the fact
that devfs was not able to be enabled anymore, and in fact, a lot of
different subsystem
Ashok Raj wrote:
> On Fri, Sep 09, 2005 at 01:41:58PM -0700, Christopher Beppler wrote:
>
>> [1.] One line summary of the problem:
>> If I deactivate a CPU with /sys/devices/system/cpux and try to
>> reactivate it, then the CPU doesn't start and the kernel prints out an
>> oops.
>>
>
>
>
When doing ioctl HDIO_DRIVE_TASKFILE, the ide_task_t's
request pointer is never set, but flagged_taskfile and
do_rw_taskfile pass it as a parameter to the prehandler.
The kernel will oops taskfile pio-out commands because of this
(taskfile pio-in doesn't use a prehandler). This fix sets the
reques
> Here is a SPI framework which tries to use the driver
> framework provided by the 2.6 kernel which you can
> play around with on any platform, even on your PC :).
An idea I've used in the refresh of my simpler patch.
More complete examples (often) help. :)
> This patch only contains a core l
Hans Reiser <[EMAIL PROTECTED]> wrote:
>
> ...
>
> Do I remember right that the submission
> deadline is a week from Monday for 2.6.14 inclusion?
Next week, supposedly.
But something like a brand new filesystem can go in pretty much any time,
as long as it compiles. Because it can't break anyone
On 9/9/05, Roger Heflin <[EMAIL PROTECTED]> wrote:
>
> I saw it mentioned before that the kernel only allows a certain
> percentage of total memory to be dirty, I thought the number was
> around 40%, and I have seen machines with large amounts of ram,
> hit the 40% and then put the writing applica
On Fri, Sep 09, 2005 at 09:08:25AM +0400, Evgeniy Polyakov wrote:
> On Thu, Sep 08, 2005 at 08:30:36PM -0700, Greg KH ([EMAIL PROTECTED]) wrote:
> > On Fri, Sep 09, 2005 at 01:30:09AM +0200, Marcel Holtmann wrote:
> > > Hi Greg,
> > >
> > > > Here are some w1 patches that have been in the -mm tree
On Sat, Sep 03, 2005 at 04:13:31PM +0200, Jean Delvare wrote:
> Hi Greg, all,
>
> > This patch doesn't apply on top of my stack, first because the
> > hardware monitoring drivers have been moved to drivers/hwmon, second
> > because the via686a driver had indentation cleanups since 2.6.12.
> >
> >
On Fri, Sep 09, 2005 at 10:59:46PM +0200, Sam Ravnborg wrote:
> Using the ':' buildin in several places is such a speedup for normal
> usage that I do not plan to replace it with anything else.
So what about adding SHELL=bash at the top-level makefile?
-- DN
Daniel
-
To unsubscribe from this list
Christoph Hellwig wrote:
> 6. remove type safe lists and type safe hash queues.
>
>> not done, it is not clear that the person asking for this represents a
>> unified consensus of lkml. Other persons instead asked that it just be
>> moved out of reiser4 code into the generic kernel code, whic
Alon Bar-Lev wrote:
it crashes the kernel with atempt to kill init or it trys to load a
memory image that was never saved
I can't get it to boot for the first time so it can save a memory image
Strange...
Have you read the documentation? use resume2 instead of resume and so on?
Suspend2 w
envctrl doesn't need unistd.h; moreover, since it declares errno static
gcc4 gets very unhappy about including unistd.h.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-m68k-8390/drivers/sbus/char/bbc_envctrl.c
RC13-git7-envctrl/drivers/sbus/char/bbc_envctrl.c
--- RC13
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-s2io-u64/drivers/scsi/ch.c
RC13-git7-scsi-ch/drivers/scsi/ch.c
--- RC13-git7-s2io-u64/drivers/scsi/ch.c2005-08-28 23:09:45.0
-0400
+++ RC13-git7-scsi-ch/drivers/scsi/ch.c 2005-09-07 13:55:19.0 -0400
@@ -56
On Friday, 9 of September 2005 10:50, rob wrote:
> Rafael J. Wysocki wrote:
>
> >On Friday, 9 of September 2005 07:09, you wrote:
> >
> >
> >>Rafael J. Wysocki wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>On Wednesday, 7 of September 2005 09:33, rob wrote:
> >>>
> >>>
> >>>
> >>>
> I
On Fri, Sep 09, 2005 at 12:21:13PM -0700, carbonated beverage wrote:
> I'm assuming some bash-isms crept into the tree, as I got these:
>
> LD net/built-in.o
> /bin/sh: +@: not found
> make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make
> rule.
Using the ':' buildi
On Fri, Sep 09, 2005 at 01:42:19PM -0700, Hans Reiser wrote:
> Chris Shoemaker wrote:
>
> >On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
> >
> >
> >>If we lose every remaining point of this list, we can generate a patch
> >>in a few days, because the VFS work was the only substant
Hi,
CONFIG_PC is defined but isn't actually used anywhere:
[EMAIL PROTECTED]:~/devel/kernel/b$ grep -rw CONFIG_PC *
arch/i386/defconfig:CONFIG_PC=y
[EMAIL PROTECTED]:~/devel/kernel/b$
My impression is that this is left-over cruft after the introduction
of CONFIG_X86_PC with the subarch spl
On Thursday 08 September 2005 14:30, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13
>-mm2/
Hi Andrew,
here is the log from my problem with an usb device (kernel hangs when
switching the external hdd on). I hope this log provides useful informati
On Fri, Sep 09, 2005 at 01:41:58PM -0700, Christopher Beppler wrote:
>
>[1.] One line summary of the problem:
>If I deactivate a CPU with /sys/devices/system/cpux and try to
>reactivate it, then the CPU doesn't start and the kernel prints out an
>oops.
>
Could you try this on 2.6
On Fri, 9 Sep 2005, Hans Reiser wrote:
> Chris Shoemaker wrote:
>
> >On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
> >
> >
> >>If we lose every remaining point of this list, we can generate a patch
> >>in a few days, because the VFS work was the only substantive (in coding
> >>hours
On 9/9/05, Hans Reiser <[EMAIL PROTECTED]> wrote:
> Chris Shoemaker wrote:
>
> >On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
> >
> >
> >>If we lose every remaining point of this list, we can generate a patch
> >>in a few days, because the VFS work was the only substantive (in codin
Running klive on a sparc.
Now I wonder: what should/can I run to help by testing a kernel? The sun
is dedicated for the testing so everything is possible.
Folkert van Heusden
--
Try MultiTail! Multiple windows with logfiles, filtered with regular
expressions, colored output, etc. etc. www.vanhe
> Date: Fri, 9 Sep 2005 11:40:39 -0600
> From: Grant Likely <[EMAIL PROTECTED]>
>
> On 9/8/05, David Brownell <[EMAIL PROTECTED]> wrote:
> > That implies whoever is registering is actually going and creating the
> > SPI devices ... and doing it AFTER the controller driver is registered.
> > I actua
On Fri, Sep 09, 2005 at 10:07:28AM -0700, Zwane Mwaikambo wrote:
> On a slightly different topic, how come we're using physflat for hotplug
> cpu?
>
> -#ifndef CONFIG_CPU_HOTPLUG
> /* In the CPU hotplug case we cannot use broadcast mode
> because that opens a race w
Rafael J. Wysocki wrote:
On Friday, 9 of September 2005 07:09, you wrote:
Rafael J. Wysocki wrote:
Hi,
On Wednesday, 7 of September 2005 09:33, rob wrote:
I singed up to this mailing list just to ask this question
I have built a 2.6.13 kernel for a toshiba tecra 500cdt
thi
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git8-base/drivers/scsi/qla2xxx/qla_dbg.c
current/drivers/scsi/qla2xxx/qla_dbg.c
--- RC13-git8-base/drivers/scsi/qla2xxx/qla_dbg.c 2005-08-28
23:09:45.0 -0400
+++ current/drivers/scsi/qla2xxx/qla_dbg.c 2005-09-08 23:
Chris Shoemaker wrote:
>On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
>
>
>>If we lose every remaining point of this list, we can generate a patch
>>in a few days, because the VFS work was the only substantive (in coding
>>hours) task, and it is done. Do I remember right that the
"Ian E. Morgan" <[EMAIL PROTECTED]> wrote:
>
> I would like to ask that the SBC8360 watchdog driver be pushed upstream from
> -mm in time for the 2.6.14-rc series.
That's in Wim's tree now.
Wim, could you please prepare a pull for Linus within the next couple of days?
-
To unsubscribe from this
I'm aware of the sysfs interface -- but neither /proc/modules nor
/sys/module/ actually really supplement the query_module api...
- iSteve
Bodo Eggert wrote:
iSteve <[EMAIL PROTECTED]> wrote:
May I then ask, why is the query_module syscall gone? And more
importantly, what replaces it, if
Rafael J. Wysocki wrote:
On Friday, 9 of September 2005 07:09, you wrote:
Rafael J. Wysocki wrote:
Hi,
On Wednesday, 7 of September 2005 09:33, rob wrote:
I singed up to this mailing list just to ask this question
I have built a 2.6.13 kernel for a toshiba tecra 500cdt
thi
On 09/09/05 16:05, Nish Aravamudan wrote:
> On 9/9/05, Luben Tuikov <[EMAIL PROTECTED]> wrote:
>
>>Signed-off-by: Luben Tuikov <[EMAIL PROTECTED]>
>
>
>
>
>
>>--- linux-2.6.13-orig/drivers/scsi/sas-class/sas_expander.c 1969-12-31
>>19:00:00.0 -0500
>>+++ linux-2.6.13/drivers/scsi
I would like to ask that the SBC8360 watchdog driver be pushed upstream from
-mm in time for the 2.6.14-rc series.
I recognise that this driver, like a lot of the watchdog drivers, is for a
piece of hardware this is present in only a very small percentage of
hardware runnig Linux. I doubt that bei
1 - 100 of 369 matches
Mail list logo
