Thanks for your well worded response, Shailabh.
Others will have to make further comments and
decisions here. You have understood what I had
to say, and responded well. I have nothing to
add at this point that would help further.
--
I won't rest till it's the best ...
Paul Jackson wrote:
Sorry for the late response - I just saw this note.
Shailabh wrote:
So if the current CPU controller
implementation is considered too intrusive/unacceptable, it can be
reworked or (and we certainly hope not) even rejected in perpetuity.
It is certainly reasonable t
I experienced this same thing (with an HPT too, I might say), and the
problem seemed to be an underpowered system. Replaced the power supply
and the problem went away.
My box had 7 HDs, all of them worked fine using a different system but I
got these errors when they where together. I thought
On Thu, Jul 28, 2005 at 02:50:24PM +0200, Helge Hafting wrote:
> I usually compile without module support. This time, I turned modules
> on in order to compile an external module.
>
> To my surprise, drivers/scsi/qla2xxx/qla2xxx.ko were built even though
> no actual modules are selected in my .c
I usually compile without module support. This time, I turned modules
on in order to compile an external module.
To my surprise, drivers/scsi/qla2xxx/qla2xxx.ko were built even though
no actual modules are selected in my .config, and the source is
not patched at all except the mm1 patch.
Helge H
On Tuesday 26 July 2005 09:03 am, Andi Kleen wrote:
> On Tue, Jul 26, 2005 at 12:12:41AM -0700, James Cleverdon wrote:
> > Here's a patch that builds on Natalie Protasevich's IRQ compression
> > patch and tries to work for MPS boots as well as ACPI. It is meant
> > for a 4-node IBM x460 NUMA box,
On Tue, Jul 26, 2005 at 12:12:41AM -0700, James Cleverdon wrote:
> Here's a patch that builds on Natalie Protasevich's IRQ compression
> patch and tries to work for MPS boots as well as ACPI. It is meant for
> a 4-node IBM x460 NUMA box, which was dying because it had interrupt
> pins with GSI
xx driver. 8-(
(Sorry about doing an attachment, but KMail is steadfastly word wrapping
inserted files. I need to upgrade)
--
James Cleverdon
IBM LTC (xSeries Linux Solutions)
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot comm
diff -pru 2.6.13-rc3-mm1/arch/i386/kernel/
Richard Purdie <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2005-07-15 at 01:36 -0700, Andrew Morton wrote:
> >
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> On the Zaurus I'm seeing a couple of false "BUG: soft
On Fri, 2005-07-15 at 01:36 -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
On the Zaurus I'm seeing a couple of false "BUG: soft lockup detected on
CPU#0!" reports. These didn't show under 2.6.12-mm1
On Sad, 2005-07-23 at 14:28 +1200, mdew wrote:
> I'm unable to mount an ext2 drive using the hpt370A raid card.
>
> upon mounting the drive, dmesg will spew these errors..I've tried
> different cables and drive is fine.
> Jul 23 01:30:21 localhost kernel: hdf: dma timeout error: status=0x25
> { D
On Gwe, 2005-07-22 at 22:47 -0400, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> Does vanilla kernel 2.6.12 work for you?
> It doesn't contain hpt366 driver update.
Its nothing to do with the driver. Read the trace Bartlomiej
> > Jul 23 01:30:21 localhost kernel: hdf: dma timeout error: status=0x25
> > if CKRM is just extensions, I think it should be an external patch.
> > if it provides a path towards unifying the many disparate RM mechanisms
> > already in the kernel, great!
>
> OK, so if it provides a path towards unifying these, what should happen
> to the old interfaces when they confli
On Sat, Jul 23, 2005 at 11:50:43PM +1200, mdew wrote:
> looks like 2.6.12 does the same sort of thing..
>
As a data-point, my dual HPT374 controllers are fine with
2.6.13-rc3-mm1. One onboard, one in a pci-slot in an Epox 4PCA3+ (socket
478, i875 chipset) motherboard.
Linux adsl-gate 2.6.
looks like 2.6.12 does the same sort of thing..
On 7/23/05, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Does vanilla kernel 2.6.12 work for you?
> It doesn't contain hpt366 driver update.
>
> Bartlomiej
>
> On 7/22/05, mdew <[EMAIL PROTECTED]> wrote:
> > I'm unable to mount
On Fri, 2005-07-22 at 20:23 -0400, Mark Hahn wrote:
> > > actually, let me also say that CKRM is on a continuum that includes
> > > current (global) /proc tuning for various subsystems, ulimits, and
> > > at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> > > being useful an
Hi,
Does vanilla kernel 2.6.12 work for you?
It doesn't contain hpt366 driver update.
Bartlomiej
On 7/22/05, mdew <[EMAIL PROTECTED]> wrote:
> I'm unable to mount an ext2 drive using the hpt370A raid card.
>
> upon mounting the drive, dmesg will spew these errors..I've tried
> different cables
> > actually, let me also say that CKRM is on a continuum that includes
> > current (global) /proc tuning for various subsystems, ulimits, and
> > at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> > being useful and fast enough to subsume the current global and per-proc
> >
On Fri, 2005-07-22 at 12:35 -0400, Mark Hahn wrote:
> actually, let me also say that CKRM is on a continuum that includes
> current (global) /proc tuning for various subsystems, ulimits, and
> at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> being useful and fast enough
Shailabh wrote:
> So if the current CPU controller
> implementation is considered too intrusive/unacceptable, it can be
> reworked or (and we certainly hope not) even rejected in perpetuity.
It is certainly reasonable that you would hope such.
But this hypothetical possibility concerns me a
On Gwe, 2005-07-22 at 12:35 -0400, Mark Hahn wrote:
> I imagine you, like me, are currently sitting in the Xen talk,
Out by a few thousand miles ;)
> and I don't believe they are or will do anything so dumb as to throw away
> or lose information. yes, in principle, the logic will need to be
Th
> > > the fast path slower and less maintainable. if you are really concerned
> > > about isolating many competing servers on a single piece of hardware, then
> > > run separate virtualized environments, each with its own user-space.
> >
> > And the virtualisation layer has to do the same job wit
On Fri, 22 Jul 2005 15:53:55 BST, Alan Cox wrote:
> On Gwe, 2005-07-22 at 00:53 -0400, Mark Hahn wrote:
> > the fast path slower and less maintainable. if you are really concerned
> > about isolating many competing servers on a single piece of hardware, then
> > run separate virtualized environme
On Gwe, 2005-07-22 at 00:53 -0400, Mark Hahn wrote:
> the fast path slower and less maintainable. if you are really concerned
> about isolating many competing servers on a single piece of hardware, then
> run separate virtualized environments, each with its own user-space.
And the virtualisation
> of the various environments. I don't think you are one of those end
> users, though. I don't think I'm required to make everyone happy all
> the time. ;)
the issue is whether CKRM (in it's real form, not this thin edge)
will noticably hurt Linux's fast-path.
-
To unsubscribe from this list:
On Fri, 22 Jul 2005 00:53:58 EDT, Mark Hahn wrote:
> > > > yes, that's the crux. CKRM is all about resolving conflicting resource
> > > > demands in a multi-user, multi-server, multi-purpose machine. this is
> > > > a
> > > > huge undertaking, and I'd argue that it's completely inappropriate
> > > yes, that's the crux. CKRM is all about resolving conflicting resource
> > > demands in a multi-user, multi-server, multi-purpose machine. this is a
> > > huge undertaking, and I'd argue that it's completely inappropriate for
> > > *most* servers. that is, computers are generally so dam
Sorry - I didn't see Mark's original comment, so I'm replying to
a reply which I did get. ;-)
On Thu, 21 Jul 2005 23:59:09 EDT, Shailabh Nagar wrote:
> Mark Hahn wrote:
> >>I suspect that the main problem is that this patch is not a mainstream
> >>kernel feature that will gain multiple uses, but
Paul Jackson wrote:
Martin wrote:
No offense, but I really don't see why this matters at all ... the stuff
in -mm is what's under consideration for merging - what's in SuSE is ...
Yes - what's in SuSE doesn't matter, at least not directly.
No - we are not just considering the CKRM that is i
Mark Hahn wrote:
I suspect that the main problem is that this patch is not a mainstream
kernel feature that will gain multiple uses, but rather provides
support for a specific vendor middleware product used by that
vendor and a few closely allied vendors. If it were smaller or
less intrusive, su
On Fri, 22 Jul 2005 13:46:37 +1000, Peter Williams wrote:
> Gerrit Huizenga wrote:
> >>I imagine that the cpu controller is missing from this version of CKRM
> >>because the bugs introduced to the cpu controller during upgrading from
> >>2.6.5 to 2.6.10 version have not yet been resolved.
> >
>
Martin wrote:
> No offense, but I really don't see why this matters at all ... the stuff
> in -mm is what's under consideration for merging - what's in SuSE is ...
Yes - what's in SuSE doesn't matter, at least not directly.
No - we are not just considering the CKRM that is in *-mm now, but also
w
l code. Or perhaps there is a more sophisticated cpu
controller in the SuSE kernel.
As there is NO CKRM cpu controller in 2.6.13-rc3-mm1 (that I can see)
the one in 2.6.5 is certainly more sophisticated :-). So the reason
that the considerable mangling of sched.c evident in SuSE's 2.6.5 k
; > ongoing improvements that CKRM is making to reduce their footprint
> > in core kernel code. Or perhaps there is a more sophisticated cpu
> > controller in the SuSE kernel.
>
> As there is NO CKRM cpu controller in 2.6.13-rc3-mm1 (that I can see)
> the one in 2.
there is NO CKRM cpu controller in 2.6.13-rc3-mm1 (that I can see)
the one in 2.6.5 is certainly more sophisticated :-). So the reason
that the considerable mangling of sched.c evident in SuSE's 2.6.5 kernel
source is not present is that the cpu controller is not included in
these patches
Paul Jackson wrote:
Matthew wrote:
Perhaps someone who knows CKRM better than I can explain why the CKRM
version in some SuSE releases based on 2.6.5 kernels has substantial
code and some large ifdef's in sched.c, but the CKRM in *-mm doesn't.
Or perhaps I'm confused. There's a good chance
Matthew wrote:
> I don't see the large ifdefs you're referring to in -mm's
> kernel/sched.c.
Perhaps someone who knows CKRM better than I can explain why the CKRM
version in some SuSE releases based on 2.6.5 kernels has substantial
code and some large ifdef's in sched.c, but the CKRM in *-mm doesn
> >>
> >> I also use 2.6.13-rc3-mm1. Will try with a previous version an report to
> >> lkml if
> >> it works.
> >>
> >
> > I just tried 13-rc2-mm1 and dri is working again. Its reported to also work
> > with 13-rc3.
>
Hmm no
On Sun, 2005-07-17 at 08:20 -0700, Paul Jackson wrote:
> It is somewhat intrusive in the areas it controls, such as some large
> ifdef's in kernel/sched.c.
I don't see the large ifdefs you're referring to in -mm's
kernel/sched.c.
> The sched hooks may well impact the cost of maintaining the sch
) RADEON(0): [drm] DRM interface version 1.2
> >> > > (II) RADEON(0): [drm] created "radeon" driver at busid
> >> > > "pci::01:00.0"
> >> > > (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc2411000
> >> > > (II)
SAREA at 0xc2411000
>> > > (II) RADEON(0): [drm] drmMap failed
>> > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
>> > >
>> > > And glxgears reports 300 frames per second. How do I get dri back? It
>> > > was workin
ts 300 frames per second. How do I get dri back? It
> > was working fine with XFree. The XF86Config-4 was changed by the upgrade
> > dropping some parms in the Device section. Restoring them has no effect
> > on the problem.
> What kernel do you use? I get the same behaviour
Well said, Mark. Thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Replace v9fs_block_bits() with fls()
Originally from Rene Scharfe.
Signed-off-by: Eric Van Hensbergen <[EMAIL PROTECTED]>
---
commit f2a177d5cc8ba35ac8473961def629890d30a2f7
tree d81534c54698cb502bf7810488b03be36f36a528
parent 76ebbc7869a06014e638ad72148c375cf6644655
author Eric Van Hensbergen <
On 7/15/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>
> Changes since 2.6.13-rc2-mm2:
>
>
> git-drm.patch
> git-audit.patch
> git-input.patch
> git-kbuild.patch
make help br0ken, missing matching `'' for binrpm-pkg.
--
Coywolf Qi Hunt
http://ahbl.org/~coywolf/
-
To unsubscribe from th
On Sat, Jul 16, 2005 at 09:32:49PM -0400, wrote:
> On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> >
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> > +suspend-update-documentation.patch
>
.
Signed-off-by: [EMAIL PROTECTED]
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
Index: linux-2.6.13-rc3-mm1/drivers/connector/Kconfig
===
--- linux-2.6.13-rc3-mm1.orig/drivers/connector/Kconfig 2005-07-18
13:35:26.0
fb.c:467: error: invalid operands to binary !=
> make[3]: *** [drivers/video/chipsfb.o] Error 1
> make[2]: *** [drivers/video] Error 2
> make[1]: *** [drivers] Error 2
> make[1]: Leaving directory
> `/usr/src/linux-ctesiphon/linux-2.6.13-rc3-mm1'
> make: *** [stamp-build]
Hi,
> > What, in your opinion, makes it "obviously unmergeable"?
Controlling resource assignment, I think that concept is good.
But the design is another matter that it seems somewhat overkilled
with the current CKRM.
> I suspect that the main problem is that this patch is not a mainstream
> ker
On Friday, 15 of July 2005 10:36, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> (http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.13-rc3-mm1.gz until
> kernel.org syncs up)
Apparently, mount does not work
On Saturday, 16 of July 2005 23:39, Andrew Morton wrote:
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > On Friday, 15 of July 2005 10:36, Andrew Morton wrote:
> > >
> > >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patc
> I suspect that the main problem is that this patch is not a mainstream
> kernel feature that will gain multiple uses, but rather provides
> support for a specific vendor middleware product used by that
> vendor and a few closely allied vendors. If it were smaller or
> less intrusive, such as a d
On Sun, Jul 17, 2005 at 10:15:44AM +0200, Miklos Szeredi wrote:
> I get the following build failure on 2.6.13-rc3-mm1. It builds fine
> on 2.6.13-rc3.
>
> Can anybody help fixing it?
>
> Thanks,
> Miklos
>
> /usr/src/quilt/linux$ make ARCH=um V=1
> if test ! /us
n a 2.6.5 variant of SuSE that I happen to be
building just now for other reasons. The source files that have 'ckrm'
in the pathname, _not_ counting Doc files, total 13044 lines of text.
The CONFIG_CKRM* config options add 144 Kbytes to the kernel text.
The CKRM patches in 2.6.13-rc3-m
I get the following build failure on 2.6.13-rc3-mm1. It builds fine
on 2.6.13-rc3.
Can anybody help fixing it?
Thanks,
Miklos
/usr/src/quilt/linux$ make ARCH=um V=1
if test ! /usr/src/quilt/linux -ef /usr/src/quilt/linux; then \
/bin/sh /usr/src/quilt/linux/scripts/mkmakefile
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
>
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
> +suspend-update-documentation.patch
> +swsusp-fix-printks-and-cleanups.patch
> +swsusp-fix-remaining-u32-vs-pm_message_t-con
Le 15.07.2005 10:36, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
Hello,
I just got this oops :
Unable to handle kernel NULL pointer dereference at virtual address 0104
printing eip:
c016c7c4
*pde =
Oops:
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> On Friday, 15 of July 2005 10:36, Andrew Morton wrote:
> >
> >
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
> >
> > (http://www.zip.com.au/
On Friday, 15 of July 2005 10:36, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> (http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.13-rc3-mm1.gz until
> kernel.org syncs up)
There seems to be a regression
Andrew Vasquez wrote:
> Yes, quite. How about the following to correct the intention.
>
>
>
> Add correct Kconfig option for ISP24xx support.
>
> Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
> ---
>
> diff --git a/drivers/scsi/qla2xxx/Kconfig b/drivers/scsi/qla2xxx/Kconfig
> --- a/driver
Hi,
On Fri, 15 Jul 2005 16:23:49 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Yoichi Yuasa <[EMAIL PROTECTED]> wrote:
> >
> > Hi Andrew
> >
> > I got the following error.
> >
> > make ARCH=mips oldconfig
> > scripts/kconfig/conf -o arch/mips/Kconfig
> > drivers/video/Kconfig:7:warning: type
Yoichi Yuasa <[EMAIL PROTECTED]> wrote:
>
> Hi Andrew
>
> I got the following error.
>
> make ARCH=mips oldconfig
> scripts/kconfig/conf -o arch/mips/Kconfig
> drivers/video/Kconfig:7:warning: type of 'FB' redefined from 'boolean' to
> 'tristate'
>
> file drivers/char/speakup/Kconfig already sc
Hi again,
On Sat, 16 Jul 2005 07:52:42 +0900
Yoichi Yuasa <[EMAIL PROTECTED]> wrote:
> Hi Andrew
>
> I got the following error.
>
> make ARCH=mips oldconfig
> scripts/kconfig/conf -o arch/mips/Kconfig
> drivers/video/Kconfig:7:warning: type of 'FB' redefined from 'boolean' to
> 'tristate'
>
>
Hi Andrew
I got the following error.
make ARCH=mips oldconfig
scripts/kconfig/conf -o arch/mips/Kconfig
drivers/video/Kconfig:7:warning: type of 'FB' redefined from 'boolean' to
'tristate'
file drivers/char/speakup/Kconfig already scanned?
make[1]: *** [oldconfig] Error 1
make: *** [oldconfig]
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
> >
> > (http://www.zip.com.au/~akpm/linux/p
Hi, Matthias Urlichs wrote:
> Also GITtable, as soon as the mirrors' work is done:
>
> http://www.kernel.org/git/?p=linux/kernel/git/smurf/v2.6.13-rc3-mm1.git;a=summary
Moved to
http://www.kernel.org/git/?p=linux/kernel/git/smurf/linux-trees.git;a=summary
--
Matthias Urlichs | {M:U} IT De
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> +update-filesystems-for-new-delete_inode-behavior-fix.patch
>
> This needs to be, too.
Applied.
Joel
--
"There are only two ways to live your life. One is as though nothing
is a miracle. The other is as though everythi
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> (http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.13-rc3-mm1.gz until
> kernel.org syncs up)
>
>
> - Added
On Fri, 15 Jul 2005, Adrian Bunk wrote:
> On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.13-rc2-mm2:
> >...
> > git-scsi-misc.patch
> >...
> > Subsystem trees
> >...
>
...
> +obj-$(CONFIG_SCSI_QLA24XX) += qla2xxx.o
>
>
> I don't know what exactly y
Grant Coady <[EMAIL PROTECTED]> wrote:
>
> On Fri, 15 Jul 2005 01:36:53 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
> Did _not_ break Yenta +
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc2-mm2:
>...
> git-scsi-misc.patch
>...
> Subsystem trees
>...
--- linux-2.6.13-rc3/drivers/scsi/qla2xxx/Makefile 2005-06-17
16:04:01.0 -0700
+++ devel/drivers/scsi/qla2xxx/Makefile 2005-07-
On Fri, 15 Jul 2005 01:36:53 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
Did _not_ break Yenta + CardBus on Toshiba ToPIC100:
http://scatter.mine.nu/test/linux-2.6/tosh/dmesg-2.6.13
Hi, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
>
Also GITtable, as soon as the mirrors' work is done:
http://www.kernel.org/git/?p=linux/kernel/git/smurf/v2.6.13-rc3-mm1.git;a=summary
... since people asked:
-
Russell King <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jul 15, 2005 at 01:56:29AM -0700, Andrew Morton wrote:
> > Russell King <[EMAIL PROTECTED]> wrote:
> > >
> > > On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> > > > +uart_handle_sysrq_char-warning-fix.patch
> > > >
> > > > Fix a
On Fri, Jul 15, 2005 at 01:56:29AM -0700, Andrew Morton wrote:
> Russell King <[EMAIL PROTECTED]> wrote:
> >
> > On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> > > +uart_handle_sysrq_char-warning-fix.patch
> > >
> > > Fix a warning
> >
> > Andrew, this requires a little more fi
Russell King <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> > +uart_handle_sysrq_char-warning-fix.patch
> >
> > Fix a warning
>
> Andrew, this requires a little more fixing than your simple patch.
> Several drivers omit 'regs' from the receive han
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
> +uart_handle_sysrq_char-warning-fix.patch
>
> Fix a warning
Andrew, this requires a little more fixing than your simple patch.
Several drivers omit 'regs' from the receive handler when sysrq is
not enabled. Hence, this simple fix
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/
(http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.13-rc3-mm1.gz until
kernel.org syncs up)
- Added the CKRM patches. This is just here for people to look at at this
stage.
Changes since 2.6.13-rc2
78 matches
Mail list logo
