* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> Ingo,
>
> I just found another deadlock in the pi_lock logic. The PI logic is
> very dependent on the P1->L1->P2->L2->P3 order. But our good old
> friend is back, the BKL.
>
> Since the BKL is let go and regrabbed even if a task is grabbing
>
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-08-29 at 01:35, Ingo Molnar wrote:
> > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> >
> > > I'm getting a build error for 2.6.13-rc7-rt4 with PREEMPT_DESKTOP for
> > > i386:
> >
> > hm, cannot reproduce this build
From: Jon Smirl <[EMAIL PROTECTED]>
Date: Tue, 30 Aug 2005 00:35:11 -0400
> As far as I can tell no one has built recent hardware this way. But I
> believe there are some old SCSI controllers that do this. I provided a
> ROM API for disabling sysfs access, if we identify one of these cards
> we
On Tue, 30 Aug 2005, Benjamin Herrenschmidt wrote:
>
> I was just testing a slightly different one that appear to fix the
> problem :
...
> + rom_addr = region.start | (res->flags & PCI_REGION_FLAG_MASK);
I worry about this one. It's not really correct. The low en bits are
"reserved", and
On Tue, 30 Aug 2005, Jon Smirl wrote:
>
> I was reading the status out of the PCI config space to account for
> our friend X which enables ROMs without informing the OS. With X
> around PCI config space can get out of sync with the kernel
> structures.
Well, yes, except that we use the
On Tue, 30 Aug 2005, Benjamin Herrenschmidt wrote:
>
> So what about fixing pci_map_rom() to call pcibios_resource_to_bus() and
> then write the resource back to the BAR ? I'm still a bit annoyed that
> we re-allocate the address while the original one was perfectly good
> (though not enabled)
>
> I was reading the status out of the PCI config space to account for
> our friend X which enables ROMs without informing the OS. With X
> around PCI config space can get out of sync with the kernel
> structures.
Well, X isn't supposed to keep the ROM enabled is it ? besides, most of
the
On Mon, Aug 29, 2005 at 10:29:00AM +0200, Ake wrote:
> I got the following Oops.
> Known problem? Fix?
Nothing known here. You can retry with -hf7 if you want, which fixes other
bugs, but I guess it will not change anything.
> The kernel is a plain 2.4.30-hf2
I have some question : what is
On 8/30/05, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, 29 Aug 2005, David S. Miller wrote:
> >
> > So I think the kernel, by not enabling the ROM, is doing the
> > right thing here.
>
> Notice that on ppc even older versions didn't actually _enable_ the rom,
> but they would write
On Mon, 2005-08-29 at 21:40 -0700, Linus Torvalds wrote:
>
> On Mon, 29 Aug 2005, David S. Miller wrote:
> >
> > So I think the kernel, by not enabling the ROM, is doing the
> > right thing here.
>
> Notice that on ppc even older versions didn't actually _enable_ the rom,
> but they would write
On 8/29/05, Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 30 Aug 2005, Benjamin Herrenschmidt wrote:
> >
> > pci_map_rom "sees" that the resource is unassigned by testing the parent
> > pointer, and calls pci_assign_resource() which, with this new patch,
> > will do nothing.
>
> Ehh..
Here is a revised version of dirent scan patch, mentioned at
following E-mail.
This patch addresses performance damages on "ls | xargs xxx" and
reverse order scan which are reported to the previous patch.
With this patch, fat_search_long() and fat_scan() use hint value
as start of scan. For
use schedule_timeout instead of direct call to schedule
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
commit 85e29936d8eab1c16120ab319cc50828f3863aba
tree a6fbb48fc860c6f5dbef0d518a500b37576caf40
parent
Base addess register for SMC 1 and 2 are never initialized.
This means that they will not work unless a bootloader already
configured them.
The DPRAM already have space reserved, this patch just makes sure
the base addess register is updated correctly on initialization.
Signed-off-by: Rune
Linas Vepstas writes:
> > One way to clean this up would be to make rpaphp the driver for the
> > EADS bridges (from the pci code's point of view).
>
> I guess I don't understand what that means. Are you suggesting moving
> pSeries_pci.c into the rpaphp code directory?
No, not at all. :)
Hi,
Is this a known problem?
Thanks,
Martin
cat /proc/sys/net/ipv4/conf/lo/rp_filter
<1>Unable to handle kernel paging request at virtual address 419a91d8
printing eip:
c0116644
*pde =
Oops: [#6]
Modules linked in:
CPU:0
EIP:0060:[]Not tainted VLI
EFLAGS: 00010246
On Mon, 2005-08-29 at 21:20 -0700, David S. Miller wrote:
> From: Linus Torvalds <[EMAIL PROTECTED]>
> Date: Mon, 29 Aug 2005 21:09:24 -0700 (PDT)
>
> > So 2.6.13 is being "safe". It allocates the space for the ROM in the
> > resource tables, but it neither enables it nor does it write the
> >
On Mon, 29 Aug 2005, David S. Miller wrote:
>
> So I think the kernel, by not enabling the ROM, is doing the
> right thing here.
Notice that on ppc even older versions didn't actually _enable_ the rom,
but they would write the non-enabled address to the PCI_ROM_ADDRESS
register, so that
> What you want is a "zombie state", where we write the partial information
> to hardware. It's what we used to do, but it's certainly no more logical
> than what it does now, and it led to problem reports.
>
> Btw, why does this happen on powerpc, but not x86? I'm running a radeon
> laptop
On 8/29/05, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> While looking there, I also noticed pci_map_rom_copy() stuff and I'm
> surprised it was ever accepted in the tree. While I can understand that
> we might need to keep a cached copy of the ROM content (due to cards
> like matrox who
Marcelo Tosatti wrote:
On Mon, Aug 29, 2005 at 11:39:02PM -0400, Jeff Garzik wrote:
Marcelo Tosatti wrote:
+static int voltage_set(int slot, int vcc, int vpp)
+{
+ u_int reg = 0;
+
+ switch(vcc) {
+ case 0: break;
+ case 33:
+ reg |= BCSR1_PCVCTL4;
+
Marcelo Tosatti writes:
> The memory map structure which contains device configuration/registers
> is _always_ directly mapped with pte's (the 8xx is a chip with builtin
> UART/network/etc functionality).
>
> I don't think there is a need to use read/write acessors.
Generally on PowerPC you
Hmm, well the PCI spec seems to be clear on the fact that PCI
interrupts should be level sensitive.
- kumar
On Aug 29, 2005, at 10:02 PM, Li Tony-r64360 wrote:
I think it is OK. The external interrupt can be edged. And it works
well
in my board.
Tony Li
-Original Message-
From:
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Mon, 29 Aug 2005 21:09:24 -0700 (PDT)
> So 2.6.13 is being "safe". It allocates the space for the ROM in the
> resource tables, but it neither enables it nor does it write the
> (disabled) address out to the device, since both of those actions have
>
My problems with ENOPROTOOPT were due to lack of coffee. They were
caused by ICMP protocol unreachable responses from the test server
because I'd taken away it's pppd. My mistake.
On Mon, Aug 29, 2005 at 05:10:34PM -0500, Matt Domsch wrote:
> I've asked James Cameron, pptp project lead, to try
On Mon, 29 Aug 2005, Linus Torvalds wrote:
>
> What you want is a "zombie state", where we write the partial information
> to hardware. It's what we used to do, but it's certainly no more logical
> than what it does now, and it led to problem reports.
Btw, the fundamental reason for the
Greetings kind hackers...
I recently switched to 2.6.13 on my desktop. I noticed that the second
"CPU" (is there a better term to use in this HyperThreading scenario?) that
used to be listed in /proc/cpuinfo is no longer present. Browsing over the
archives, it appears as if someone else
On Mon, Aug 29, 2005 at 11:39:02PM -0400, Jeff Garzik wrote:
> Marcelo Tosatti wrote:
> >+static int voltage_set(int slot, int vcc, int vpp)
> >+{
> >+u_int reg = 0;
> >+
> >+switch(vcc) {
> >+case 0: break;
> >+case 33:
> >+reg |= BCSR1_PCVCTL4;
> >+break;
On Tue, 30 Aug 2005, Benjamin Herrenschmidt wrote:
>
> Ok, it won't do nothing in fact. It's worse. It will return 0 (success),
> will actually assign a completely new address to the resource, will
> update the resource structure ... and will _not_ update the PCI resource
> BAR for the ROM.
>
Yes. I did also report it (see http://lkml.org/lkml/2005/8/26/252)
cheers,
Masoud Sharbiani
Lee Revell wrote:
On Mon, 2005-08-29 at 14:23 -0400, Masoud Sharbiani wrote:
Sadly, with 2.6.13 (as in with 2.6.13-rc7), it crashes on boot, on a
dual P3 machine
It works just fine when compiled
On Tue, 30 Aug 2005 12:54 pm, Theodore Ts'o wrote:
> On Tue, Aug 30, 2005 at 10:05:06AM +1000, Con Kolivas wrote:
> > On Tue, 30 Aug 2005 08:42, Christopher Friesen wrote:
> > > Lee Revell wrote:
> > > > The controversy over the introduction of CONFIG_HZ demonstrated the
> > > > urgency of getting
Marcelo Tosatti wrote:
+static int voltage_set(int slot, int vcc, int vpp)
+{
+ u_int reg = 0;
+
+ switch(vcc) {
+ case 0: break;
+ case 33:
+ reg |= BCSR1_PCVCTL4;
+ break;
+ case 50:
+ reg |= BCSR1_PCVCTL5;
+ break;
+
Ingo,
I just found another deadlock in the pi_lock logic. The PI logic is
very dependent on the P1->L1->P2->L2->P3 order. But our good old friend
is back, the BKL.
Since the BKL is let go and regrabbed even if a task is grabbing another
lock, it messes up the order. For example, it can do the
On Mon, 29 Aug 2005, Rusty Lynch wrote:
> So, assuming inlining the notifier_call_chain would address Christoph's
> conserns, is the following patch something like what you are sugesting?
> This would make all the kdebug.h::notify_die() calls use the inline version.
Please do not generate any
> pci_map_rom "sees" that the resource is unassigned by testing the parent
> pointer, and calls pci_assign_resource() which, with this new patch,
> will do nothing.
Ok, it won't do nothing in fact. It's worse. It will return 0 (success),
will actually assign a completely new address to the
Frank Cusack, primary author of the ppp_mppe kernel module, is no
longer at Google. This updates his email address in the module, as
agreed to by Frank privately.
ppp_mppe.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Signed-off-by: Matt Domsch <[EMAIL PROTECTED]>
--
Matt
James Bottomley wrote:
On Tue, 2005-08-30 at 10:56 +1000, Nick Piggin wrote:
Gang lookup is mainly used on IO paths but also on truncate,
which is a reasonably fast path on some workloads (James,
this is my suggestion for what you should test - truncate).
Actually, I don't think I can
On Tue, 30 Aug 2005, Benjamin Herrenschmidt wrote:
>
> pci_map_rom "sees" that the resource is unassigned by testing the parent
> pointer, and calls pci_assign_resource() which, with this new patch,
> will do nothing.
Ehh.. It didn't do anything with the old code either for that case, so
Hello,
During the Kernel Summit somebody raised the point that it's not clear
how much testing each rc/pre/git kernel gets before the final release.
So I setup a server to track automatically the amount of testing that
each kernel gets. Clearly this will be a very rough approximation and it
Paul Jackson <[EMAIL PROTECTED]> wrote:
>
> md-fix-rh_dec-rh_inc-race-in-dm-raid1c.patch # wait
>
> ...
> Question - should I be asking Andrew not to comment this way, or
> should I be asking quilt to recognize a comment convention here?
I'll just stop using them.
-
To unsubscribe from
As I said in "[RFC] FAT dirent scan with hint"
<[EMAIL PROTECTED]>, we realized that FAT/VFAT has
poor performance with scanning directory entries.
Per discussions with Ogawa-san, VFAT maintainer, I took profiling data
to seek better solution. Here are results attached.
In short, I
I think it is OK. The external interrupt can be edged. And it works well in my
board.
Tony Li
-Original Message-
From: Gala Kumar K.-galak
Sent: Tuesday, August 30, 2005 1:43 AM
To: Li Tony-r64360
Cc: linuxppc-embedded; linux-kernel@vger.kernel.org; Gala Kumar K.-galak; Chu
Hi,
Here goes the 8xx PCMCIA driver, originally written by Magnus Damm, with
several improvements and fixes.
The driver was merged in v2.4 but never forward ported to v2.6.
Please review, comments are welcome (including aesthetic enhancements).
Russell: The driver is using
On Tue, Aug 30, 2005 at 10:05:06AM +1000, Con Kolivas wrote:
> On Tue, 30 Aug 2005 08:42, Christopher Friesen wrote:
> > Lee Revell wrote:
> > > The controversy over the introduction of CONFIG_HZ demonstrated the
> > > urgency of getting a dynamic tick solution merged before 2.6.14.
> > >
> > >
> Date: Sun, 21 Aug 2005 00:33:48 +0100 (BST)
> From: Mark Underwood <[EMAIL PROTECTED]>
>
> ...
> Interestingly (we for me at least ;-) I have been
> working on an SPI subsystem that was/is a copy of the
> I2C subsystem with changes as SPI doesn't have a
> protocol like I2C. ...
>
> To me, what I
On Tue, 2005-08-30 at 10:56 +1000, Nick Piggin wrote:
> Sonny Rao wrote:
>
> >On Mon, Aug 29, 2005 at 01:37:48PM +1000, Nick Piggin wrote:
> >
> >>s/common/only ?
> >>
> >>But the page tree is indexed by file offset rather than virtual
> >>address, and we try to span the file's pagecache with the
On Fri, 2005-08-26 at 11:59 -0700, Linux Kernel Mailing List wrote:
> tree d8b7aaaec93de93841b46e8e05a3b454d05bd357
> parent 26aad69e3dd854abe9028ca873fb40b410a39dd7
> author Linus Torvalds <[EMAIL PROTECTED]> Sat, 27 Aug 2005 00:49:22 -0700
> committer Linus Torvalds <[EMAIL PROTECTED]> Sat, 27
The last couple times SPI frameworks came up here, some of the feedback
included "make it use the driver model properly; don't be like I2C".
In hopes that it'll be useful, here's a small SPI core with driver model
support driven from board-specific tables listing devices. I expect the
I/O
Apparently Andrews patch tools allow trailing comments on active lines
in the series file, as in these lines culled from the series file for
2.6.13-rc6-mm2:
e1000-numa-aware-allocation-of-descriptors-v2.patch # hold
nfs-nfs3-page-null-fill-in-a-short-read-situation.patch # wait
On Mon, 2005-08-29 at 18:45, Lee Revell wrote:
> On Mon, 2005-08-29 at 18:15 -0700, Fernando Lopez-Lezcano wrote:
> > On Mon, 2005-08-29 at 01:35, Ingo Molnar wrote:
> > > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > >
> > > > I'm getting a build error for 2.6.13-rc7-rt4 with
Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> But of course gang lookup is only useful if a single read() call
> asks for more than 1 page - is that a performance critical path?
readahead should do gang lookups (or, preferably, find-next, when it's
implemented). But nobody got around to it.
-
To
Andi Kleen <[EMAIL PROTECTED]> writes:
> On Tuesday 30 August 2005 02:20, Eric W. Biederman wrote:
>> PAT (or setting caching policy in the page table entries) has been a
>> long desired feature in the kernel and as large memory sizes become
>> more prevalent it becomes increasingly hard to
On Jul 27, 2005, at 2:57 PM, Andrew Morton wrote:
Kumar Gala <[EMAIL PROTECTED]> wrote:
The following board ports are no longer maintained or have become
obsolete:
adir
ash
beech
cedar
ep405
k2
mcpn765
menf1
oak
pcore
rainier
redwood
sm850
spd823ts
We are there for
On Mon, 2005-08-29 at 18:15 -0700, Fernando Lopez-Lezcano wrote:
> On Mon, 2005-08-29 at 01:35, Ingo Molnar wrote:
> > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> >
> > > I'm getting a build error for 2.6.13-rc7-rt4 with PREEMPT_DESKTOP for
> > > i386:
> >
> > hm, cannot reproduce
Sonny Rao wrote:
On Mon, Aug 29, 2005 at 01:37:48PM +1000, Nick Piggin wrote:
s/common/only ?
But the page tree is indexed by file offset rather than virtual
address, and we try to span the file's pagecache with the smallest
possible tree. So it will tend to make the trees taller.
I did
On Monday 29 August 2005 23:48, John W. Linville wrote:
> Perhaps...but I think that sounds more like a discussion of _how_ to
> implement the API, rather than _whether_ it should be implemented.
> Using some new variant of the swiotlb_* API might be appropriate
> for the x86_64 implementation.
On Tuesday 30 August 2005 02:19, Rusty Lynch wrote:
>
> So, assuming inlining the notifier_call_chain would address Christoph's
> conserns, is the following patch something like what you are sugesting?
Yes.
Well in theory you could make fast and slow notify_die too, but that's
probably not
On Mon, 29 Aug 2005 09:12:08 -0700,
Tom Rini <[EMAIL PROTECTED]> wrote:
>
>This adds hardware breakpoint support for i386. This is not as well tested as
>software breakpoints, but in some minimal testing appears to be functional.
Hardware breakpoints must be per cpu, not global. Also you will
On Tue, 30 Aug 2005, Nick Piggin wrote:
>
> Andrew, did you pick up the patch or should I resend to someone?
I picked it up. If it causes performance regressions, we can fix them, and
if it causes other problems then that will be interesting in itself.
Linus
-
To unsubscribe
Ray Fucillo wrote:
Nick Piggin wrote:
How does the following look? (I changed the comment a bit). Andrew,
please
apply if nobody objects.
Nick, I applied this latest patch to a 2.6.12 kernel and found that it
does resolve the problem. Prior to the patch on this machine, I was
seeing
On Mon, 29 Aug 2005, Ray Fucillo wrote:
>
> FWIW, an interesting side effect of this occurs when I run the database
> with this patch internally on a Linux server that uses NIS. Its an
> unrelated problem and not a kernel problem. Its due to the children
> calling initgroups()...
PAT (or setting caching policy in the page table entries) has been a
long desired feature in the kernel and as large memory sizes become
more prevalent it becomes increasingly hard to specify all of the
regions that need write-back caching with just 8 MTRRs much less add
in the write-combining
On Sat, Aug 27, 2005 at 02:24:25AM +0200, Andi Kleen wrote:
> On Saturday 27 August 2005 01:05, Christoph Lameter wrote:
> > On Fri, 26 Aug 2005, Rusty Lynch wrote:
> > > Just to be sure everyone understands the overhead involved, kprobes only
> > > registers a single notifier. If kprobes is
Hi, Jean,
Em Qui, 2005-08-25 às 00:19 +0200, Jean Delvare escreveu:
> Hi Mauro,
>
> > That's not true. We keep V4L tree compatible with older kernel
> > releases. Each change like this does generate a lot of work at V4L
> > side to provide #ifdefs to check for linux version and provide a
> >
On Tue, 30 Aug 2005 08:42, Christopher Friesen wrote:
> Lee Revell wrote:
> > The controversy over the introduction of CONFIG_HZ demonstrated the
> > urgency of getting a dynamic tick solution merged before 2.6.14.
> >
> > Anyone care to give a status report? Con, do you feel that the last
> >
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
> El Tue, 30 Aug 2005 01:34:25 +0200,
> Jesper Juhl <[EMAIL PROTECTED]> escribió:
>
> > I don't see why we should break a bunch of drivers by doing that.
> > Much better, in my oppinion, to fix the few remaining drivers still
> > using
> There it is.
2.6.13 does not boot in my PPC (iBook, 500 MHz), it hangs just at the very
begining and the machines is automatically rebooted after a couple of
minutes.
The on-screen messages finishes with a few "openpic" messages:
http://mnm.uib.es/gallir/tmp/linux-13-ppc.jpg
I used the
When I try to compile 2.6.13, using a complete tarball from
kernel.org, the compilation fails with:
---
SYSMAP System.map
SYSMAP .tmp_System.map
Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
make: *** [vmlinux]
El Tue, 30 Aug 2005 01:34:25 +0200,
Jesper Juhl <[EMAIL PROTECTED]> escribió:
> I don't see why we should break a bunch of drivers by doing that.
> Much better, in my oppinion, to fix the few remaining drivers still
> using check_region and *then* kill it. Even unmaintained drivers may
I'd
manomugdha biswas wrote:
Hi,
I am using the following makefile and the .c file to
generate a kernel module. I can load this module
without error and warning. But when I call ioctl()
from user application to run this module it gets
kernel panic!
I think there's something wrong with the way
On Mon, Aug 29, 2005 at 05:10:34PM -0500, Matt Domsch wrote:
> I've asked James Cameron, pptp project lead, to try a test to force
> the server side to issue a CCP DOWN, to make sure the client-side
> kernel ppp_generic module does the right thing and drops packets.
I'm still working on this;
On 8/30/05, Diego Calleja <[EMAIL PROTECTED]> wrote:
[snip]
>
> /me wonders why check_region has not been killed, it has been
> deprecated for years; killing it would force developers to fix it
> and would help to identify unmaintained drivers...
I don't see why we should break a bunch of
Nick Piggin wrote:
How does the following look? (I changed the comment a bit). Andrew, please
apply if nobody objects.
Nick, I applied this latest patch to a 2.6.12 kernel and found that it
does resolve the problem. Prior to the patch on this machine, I was
seeing about 23ms spent in fork
On Maw, 2005-08-30 at 00:40 +0200, Daniele Orlandi wrote:
> So, who is the copyright holder of that file, so that I can ask him
> permission
> to use the file in a Lesser GPL project?
Linus I believe for the most part. I wrote the prefetching changes to
for_each_ functions and I'd consider
El Tue, 30 Aug 2005 01:14:17 +0200,
Stephane Wirtel <[EMAIL PROTECTED]> escribió:
> Is there a function to replace this deprecated function ?
request_region
> Why is it deprecated ?
>From http://lists.osdl.org/pipermail/kernel-janitors/2004-January/000346.html:
"The reason that check_region()
On 8/30/05, Stephane Wirtel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
[snip]
>
> Is there a function to replace this deprecated function ?
>
Yes, you just call request_region() and check its
On Tue, 30 Aug 2005, Stephane Wirtel wrote:
> Hi,
>
> By compiling my kernel, I can see that the __check_region function (in
> kernel/resource.c) is deprecated.
>
> With a grep on the source code of the last release, I get this result.
>
> drivers/pnp/resource.c:255: if
On Mon, 29 Aug 2005 12:24:18 -0500, "Miller, Mike (OS Dev)" <[EMAIL PROTECTED]>
wrote:
>
>> This is after my minimal sas transport class, please also
>> read the thread about it on linux-scsi
>>
>In the referenced code for using sysfs, there only appear to be methods
>for reading attributes.
Fix compiler warning in drivers/scsi/aic7xxx/aic7770.c :
drivers/scsi/aic7xxx/aic7770.c:129: warning: unused variable `l'
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
drivers/scsi/aic7xxx/aic7770.c |1 -
1 files changed, 1 deletion(-)
---
> "Holger" == Holger Kiehl <[EMAIL PROTECTED]> writes:
Holger> Hello I have a system with the following setup:
(4-way CPUs, 8 spindles on two controllers)
Try using XFS.
See http://scalability.gelato.org/DiskScalability_2fResults --- ext3
is single threaded and tends not to get the
Hi Jesper,
> Hmm, neither do I. Looking in MAINTAINERS I don't see anybody, and
> looking in the sources I find just a company name `Neterion'.
> So, lacking an email address for a maintainer, sending your patch to
> linux-kernel is the right thing to do (even if you had found a
> maintainer,
Warning fix :
drivers/isdn/i4l/isdn_v110.c:523: warning: `ret' might be used uninitialized
in this function
Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
---
drivers/isdn/i4l/isdn_v110.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
Ping... any objection to this?
CONFIG_IDE_MAX_HWIFS is a generic thing, no need to have it duplicated
by every arch that uses it.
Signed-off-by: Bjorn Helgaas <[EMAIL PROTECTED]>
Index: work-ide/include/asm-alpha/ide.h
===
---
On 8/30/05, Stephane Wirtel <[EMAIL PROTECTED]> wrote:
> Hi all ,
>
> Sorry if I don't send this patch to the maintainer of s2io, but I don't
> know who is he.
>
Hmm, neither do I. Looking in MAINTAINERS I don't see anybody, and
looking in the sources I find just a company name `Neterion'.
So,
Lee Revell wrote:
The controversy over the introduction of CONFIG_HZ demonstrated the
urgency of getting a dynamic tick solution merged before 2.6.14.
Anyone care to give a status report? Con, do you feel that the last
version you posted is ready to go in?
Last time I got interested in this,
On Fri, 26 Aug 2005, Matt Mackall wrote:
> On Tue, Aug 16, 2005 at 02:32:01PM +0200, Michal Schmidt wrote:
> > Ingo Molnar wrote:
> > >i've released the 2.6.13-rc6-rt1 tree, which can be downloaded from the
> > >usual place:
> > >
> > > http://redhat.com/~mingo/realtime-preempt/
> > >
> > >as
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
mpc85xx_cds_common.c | 11 +++
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/arch/ppc/platforms/85xx/mpc85xx_cds_common.c
b/arch/ppc/platforms/85xx/mpc85xx_cds_common.c
---
On Mon, Aug 29, 2005 at 12:24:18PM -0500, Miller, Mike (OS Dev) wrote:
>
> > This is after my minimal sas transport class, please also
> > read the thread about it on linux-scsi
> >
> In the referenced code for using sysfs, there only appear to be methods
> for reading attributes. How about if
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
pci.c | 21 +++--
1 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/arch/ppc/kernel/pci.c b/arch/ppc/kernel/pci.c
--- a/arch/ppc/kernel/pci.c
+++ b/arch/ppc/kernel/pci.c
@@
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
ebus.c | 17 ++---
1 files changed, 6 insertions(+), 11 deletions(-)
diff --git a/arch/sparc64/kernel/ebus.c b/arch/sparc64/kernel/ebus.c
--- a/arch/sparc64/kernel/ebus.c
+++
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
sys_sio.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/alpha/kernel/sys_sio.c b/arch/alpha/kernel/sys_sio.c
--- a/arch/alpha/kernel/sys_sio.c
+++
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
pci-frv.c |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/frv/mb93090-mb00/pci-frv.c b/arch/frv/mb93090-mb00/pci-frv.c
--- a/arch/frv/mb93090-mb00/pci-frv.c
+++
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
pci-irq.c |4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/frv/mb93090-mb00/pci-irq.c b/arch/frv/mb93090-mb00/pci-irq.c
--- a/arch/frv/mb93090-mb00/pci-irq.c
+++
The controversy over the introduction of CONFIG_HZ demonstrated the
urgency of getting a dynamic tick solution merged before 2.6.14.
Anyone care to give a status report? Con, do you feel that the last
version you posted is ready to go in?
Lee
-
To unsubscribe from this list: send the line
Generated in 2.6.13-rc6-mm2 kernel version.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
sys_alcor.c |3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/alpha/kernel/sys_alcor.c b/arch/alpha/kernel/sys_alcor.c
--- a/arch/alpha/kernel/sys_alcor.c
+++
Hi all ,
Sorry if I don't send this patch to the maintainer of s2io, but I don't
know who is he.
This patch is based on Kernel 2.6.13 release from the Linus tree.
Is there a process to send patch to the mailing list ?
Best regards,
Stephane
--
Stephane Wirtel <[EMAIL PROTECTED]>
Set of patches, which removes pci_find_device from arch subtree.
alpha/kernel/sys_alcor.c|3 ++-
alpha/kernel/sys_sio.c |6 +++---
frv/mb93090-mb00/pci-frv.c |8 ++--
frv/mb93090-mb00/pci-irq.c |4 +---
On Mon, Aug 29, 2005 at 06:12:20PM +0100, Daniel Drake wrote:
> Hi,
>
> If there are no known issues it would be nice to push this for inclusion in
> 2.6.14. The relevant patches from -mm are named
> ppp_mppe-add-ppp-mppe-encryption-module.patch and
>
On Aug 29, 2005, at 1:07 PM, Dan Malek wrote:
On Aug 29, 2005, at 1:42 PM, Kumar Gala wrote:
diff --git a/arch/ppc/platforms/83xx/mpc834x_sys.c
b/arch/ppc/platforms/83xx/mpc834x_sys.c
--- a/arch/ppc/platforms/83xx/mpc834x_sys.c
+++ b/arch/ppc/platforms/83xx/mpc834x_sys.c
@@ -62,9 +62,29 @@
>-Original Message-
>From: Ingo Oeser [mailto:[EMAIL PROTECTED]
>Sent: Saturday, August 27, 2005 5:23 AM
>To: Pallipadi, Venkatesh
>Cc: linux-kernel; Andrew Morton; Brown, Len
>Subject: Re: [PATCH] acpi: Handle cpu_index greater than 256
>properly in processor_core.c
>
>Hi Venkatesh,
>
1 - 100 of 530 matches
Mail list logo
