On Tue, 20 Nov 2007 13:32:06 +0100
Richard MUSIL <[EMAIL PROTECTED]> wrote:
> >> + if (chip->vendor.release)
> >> + chip->vendor.release(dev);
> >> +
> >> + /* it *should* be: chip->release != NULL */
> >
> > And that one's actually wrong in the context of kernel coding practices.
>
> Actually, we already established on IRC that the lasi700 driver doesn't
> need this, principally because the parisc architecture doesn't do an
> invalidate for DMA_FROM_DEVICE but a flush and invalidate
> (architecturally, if you read our manuals, even pdc is entitled to write
> back dirty
> unknown-linux-gnu/bin/ld: section .data.patch [a500 ->
> a507] overlaps section .dynamic [a3c8 ->
> a507]
Andrew Morton saw a similar thing and proposed
- . = GATE_ADDR + 0x500;
+ . = GATE_ADDR + 0x600;
in gate.lds.S ... which does
On Tue, Nov 20, 2007 at 12:49:49PM -0500, Salyzyn, Mark wrote:
> Jonathan McDowell sez:
> > On Tue, Nov 20, 2007 at 11:35:26AM -0500, James Smart wrote:
> > > The hearburn I have with these patches is that you are changing
> > > driver-specific attributes, not common ones as enforced/requested
> >
Arjan van de Ven wrote:
On Wed, 21 Nov 2007 02:43:46 +1100
Nick Piggin <[EMAIL PROTECTED]> wrote:
On Wednesday 21 November 2007 01:47, Arjan van de Ven wrote:
On Tue, 20 Nov 2007 18:37:39 +1100
Nick Piggin <[EMAIL PROTECTED]> wrote:
actually no. IRQ balancing is not a "fast" decision;
On Mon, 2007-11-19 at 16:17 +0100, Ingo Molnar wrote:
> By popular demand, here is release -v24 of the CFS scheduler patch.
>
> It is a full backport of the latest & greatest scheduler code to
> v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7. The patches can be
> downloaded from the usual place:
On Tue, Nov 20, 2007 at 02:04:02AM +, Matthew Garrett wrote:
> On Mon, Nov 19, 2007 at 03:32:25PM -0800, Gary Hade wrote:
>
> > Alex, What I was trying to suggest is a boot-time kernel option,
> > not a kernel configuration option. The basic idea is to give
> > the user (with a single
Hi Joe,
On Mon, 19 Nov 2007 17:48:08 -0800, Joe Perches wrote:
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
> ---
> drivers/i2c/busses/i2c-davinci.c |4 ++--
> drivers/i2c/busses/i2c-omap.c|6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
> (...)
Good catch. Patch
> I like the idea, but I would prefer to have three checkboxes for this option:
Nice addition, thanks for the input.
--- linux-2.6.23.8/fs/Kconfig 2007-11-16 19:14:27.0 +0100
+++ linux-2.6.23.8-dhr/fs/Kconfig 2007-11-20 19:54:54.0 +0100
@@ -918,6 +918,36 @@
help
On 20-11-07 19:00, Alan Cox wrote:
On Tue, 20 Nov 2007 18:52:04 +0100
Thomas Renninger <[EMAIL PROTECTED]> wrote:
Pass struct pnp_dev to pnp_clean_resource_table for cleanup reasons
Again I don't see the point of this change. A routine for cleaning up
resource tables expects logically to be
Hi,
I get the following build error when compiling 2.6.24-rc3-git1 for ia64
with gcc 3.4.5.
/opt/crosstool/gcc-3.4.5-glibc-2.3.6/ia64-unknown-linux-gnu/bin/ia64-unknown-linux-gnu-gcc
-nostdlib -shared -s -Wl,-soname=linux-gate.so.1
-Wl,-T,arch/ia64/kernel/gate.lds arch/ia64/kernel/gate.o -o
On Tue, 2007-11-20 at 14:14 +1100, Benjamin Herrenschmidt wrote:
> FYI, Here's what I have for the SCSI change. I haven't updated drivers
> to care for the new return code though, help appreciated with that as I
> don't know much about these drivers.
It looks to me like the return problem could
Hi all,
Please ignore the previous patch with the same subject.
It has a bug that can manifest itself in the very exotic case
when each do {} while() iteration executes on different cpu
leading to potentially infinite loop.
This is a patch based on the Ingo's idea/patch to track
delay_tsc()
On Tue, 20 Nov 2007 17:09:35 +0100
Mikael Ståldal <[EMAIL PROTECTED]> wrote:
> Hello.
>
> > The proper way to enable port <= 1024 binding support is adding
> > CAP_NET_BIND_SERVICE
> > to the process capability set, e.g. by using file-system capabilities.
>
> Is file-system capabilites part
On Tue, 20 Nov 2007, Takashi Iwai wrote:
> At Mon, 19 Nov 2007 19:35:09 +0100 (CET),
> Jaroslav Kysela wrote:
> >
> >
> > Linus, please pull from [the linus branch at]:
> >
> > master.kernel.org:/pub/scm/linux/kernel/git/perex/alsa.git linus
> > gitweb interface:
> >
Nick Piggin <[EMAIL PROTECTED]> writes:
>
> For that matter, I'd like to know why it has been decided that the
> best place for IRQ balancing is in userspace.
There is a lot of possible policy in it
> It should be in kernel
> IMO, and it would probably allow better power saving, performance,
>
I think it may be time to move away from that by now misleading
"msync(2) bug(?), returns AOP_WRITEPAGE_ACTIVATE to userland" thread.
And I've cut most out of the Cc list, but by all means add any back.
On Saturday I said:
> I'm glad to report that this unionfs, not the one in 2.6.24-rc2-mm1
>
Zach Brown wrote:
That's only because you're being, deliberately or accidentally, vague
about what your actual (as opposed to imagined) requirements are.
Maybe I can help by summarizing how syslets fit in to this.
Currently the syslet patches add a single submission call which includes
an
On Wed, 21 Nov 2007 02:43:46 +1100
Nick Piggin <[EMAIL PROTECTED]> wrote:
> On Wednesday 21 November 2007 01:47, Arjan van de Ven wrote:
> > On Tue, 20 Nov 2007 18:37:39 +1100
> >
> > Nick Piggin <[EMAIL PROTECTED]> wrote:
> > > > actually no. IRQ balancing is not a "fast" decision; every
> >
I just had a strange freeze that killed networking and made software
RAID fail two of my harddisks.
There are a bunch of messages from the kernel which I extracted from
the system log after reboot at the end of this mail. I hit power off
in pure paranoia after the box froze, and then started to
--- Casey Schaufler <[EMAIL PROTECTED]> wrote:
> From: Casey Schaufler <[EMAIL PROTECTED]>
>
> ...
I have verified this version against broken-out-2007-11-20-01-45
as well. Compiles, boots, and passes tests.
Thank you.
Casey Schaufler
[EMAIL PROTECTED]
-
To unsubscribe from this list: send
On Mon, 19 Nov 2007 15:22:11 +, Alan Cox <[EMAIL PROTECTED]> wrote:
> Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
This looks good, but have a couple of comments. Maybe I can fix it up.
> * we do not know how to support. We ignore them for the moment.
> * XXX Rate-limit the error
On Mon, Nov 19, 2007 at 03:03:48PM -0800, Fenghua Yu wrote:
>
> This patch adds and changes a few sanity checks in dmar.c.
>
> 1. The haw field in ACPI DMAR table in VT-d spec doesn't describe the range of
> haw. But since DMA page size is 4KB in DMA remapping, haw should be at least
> 4KB. The
Alan Cox <[EMAIL PROTECTED]> writes:
>
> Is it actually even worth changing in the first place ? You seem to be
> complicating the code not simplyifying it, and at the end of the day
> ISAPnP is obsolete and BIOS PnP is obsoleted by ACPI
The PNP interface is used by the ACPI code to tell the
Simplify the hot-path (gpio value get/set) locking by taking advantage
of the fact that gpio_request() effectively locks that GPIO in memory.
This also helps avoid the belated complaints about whether this locking
is one of the places raw spinlocks are OK to use; it's now back to
using regular
(resending this one to the list).
Arjan van de Ven wrote:
On Tue, 20 Nov 2007 10:47:24 -0500
Mark Lord <[EMAIL PROTECTED]> wrote:
..
After reading some of the replies, I installed it on my
malfunctioning 64-bit system, but discovered it does not perform
nearly as well as the kernel solution
On Tue, Nov 20, 2007 at 13:52:52 +0100, Alessandro Suardi wrote:
> On Nov 20, 2007 7:52 AM, Herbert Xu <[EMAIL PROTECTED]> wrote:
> > On Mon, Nov 19, 2007 at 10:47:59PM -0800, H. Peter Anvin wrote:
> > >
> > > This one is definitely messy. There is absolutely no way to know what
> > > gcc has
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Dan Williams <[EMAIL PROTECTED]>
patch 0b5316769774d1dc2fdd702e095f9e6992af269a in mainline.
ipw2200 makes extensive use of background scanning when unassociated or
down. Unfortunately, the
On Tue, Nov 20, 2007 at 10:22:48AM -0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 2.6.23.9 release.
> There are 29 patches in this series, all will be posted as a response to
> this one. If anyone has any issues with these being applied, please let
> us
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Phil Dibowitz <[EMAIL PROTECTED]>
patch 16eb345f4d9189b59bae576ae63cba7ca77817b2 in mainline.
Upgrade the unusual_devs.h file to support the Nikon D200
Signed-off-by: Mike Pagano <[EMAIL
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Ortwin Gl??ck <[EMAIL PROTECTED]>
patch d466a9190ff1ceddfee50686e61d63590fc820d9 in mainline.
Not surprisingly the Nikon D40X DSC needs the same quirks as the D40,
but it has a separate ID.
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Ingo Molnar <[EMAIL PROTECTED]>
patch a3b13c23f186ecb57204580cc1f2dbe9c284953a in mainline.
sched_clock() is not a reliable time-source, use cpu_clock() instead.
Signed-off-by: Ingo Molnar
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Ingo Molnar <[EMAIL PROTECTED]>
This is a merge of commits a5f2ce3c6024a5bb895647b6bd88ecae5001020a and
43581a10075492445f65234384210492ff333eba in mainline to fix a warning in
the 2.6.23.3
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: David P. Reed <[EMAIL PROTECTED]>
patch fa6a1a554b50cbb7763f6907e6fef927ead480d9 in mainline.
ntp: fix typo that makes sync_cmos_clock erratic
Fix a typo in ntp.c that has caused updating of
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: David P. Reed <[EMAIL PROTECTED]>
patch c399da0d97e06803e51085ec076b63a3168aad1b in mainline.
x86: fix freeze in x86_64 RTC update code in time_64.c
Fix hard freeze on x86_64 when the ntpd
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Andrey Mirkin <[EMAIL PROTECTED]>
patch 1c5b5cfd290b6cb7c67020ef420e275f746a7236 in mainline.
x86: return correct error code from child_rip in x86_64 entry.S
Right now register edi is just
From: Joe Perches <[EMAIL PROTECTED]>
Add missing space between merged string constants.
Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
---
arch/um/drivers/vde_user.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
Simplify the page fault stub by not masking signals while it is
running. This allows it to signal that it is done by executing an
instruction which will generate a SIGTRAP (int3 on x86) rather than
running sigreturn by hand after queueing a blocked SIGUSR1.
userspace_tramp now no longer puts
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Huang, Ying <[EMAIL PROTECTED]>
patch 84e0fdb1754d066dd0a8b257de7299f392d1e727 in mainline.
x86: NX bit handling in change_page_attr()
This patch fixes a bug of
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Andrew Hastings <[EMAIL PROTECTED]>
patch 801916c1b369b637ce799e6c71a94963ff63df79 in mainline.
x86: fix off-by-one in find_next_zero_string
Fix an off-by-one error in find_next_zero_string
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Kirill Korotaev <[EMAIL PROTECTED]>
patch c1217a75ea102d4e69321f210fab60bc47b9a48e in mainline.
x86: mark read_crX() asm code as volatile
Some gcc versions (I checked at least 4.1.1 from
UML was panicing in the case of failures of libc calls which shouldn't
happen. This is an overreaction since a failure from libc doesn't
normally mean that kernel data structures are in an unknown state.
Instead, the current process should just be killed if there is no
way to recover.
The case
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Jan Beulich <[EMAIL PROTECTED]>
patch aa506dc7b12d03fbf8fd11aab752aed1aadd9c07 in mainline.
i386: avoid temporarily inconsistent pte-s
One more of these issues (which were considered fixed a
These four patches are cleanups and should hold off until 2.6.25.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Some register accessor cleanups -
userspace() was calling restore_registers and save_registers for no
reason, since userspace() is on the libc side of the house, and these
add no value over calling ptrace directly
init_thread_registers and get_safe_registers were the same thing,
so
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Herbert Xu <[EMAIL PROTECTED]>
It's upstream changeset ef19454bd437b2ba14c9cda1de85debd9f383484.
[LIB] crc32c: Keep intermediate crc state in cpu order
crypto/crc32.c:chksum_final() is
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Chuck Ebbert <[EMAIL PROTECTED]>
No patch in mainline as this logic has been removed from 2.6.24 so it is
not necessary.
https://bugzilla.redhat.com/show_bug.cgi?id=340161
The problem code
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Sebastian Siewior <[EMAIL PROTECTED]>
patch 2e21630ddc3fb717dc645356b75771c6a52dc627 in mainline.
Currently the Geode AES module fails to encrypt or decrypt if
the coherent bits are not set
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Alexey Starikovskiy <[EMAIL PROTECTED]>
patch 63f0edfc0b7f8058f9d3f9b572615ec97ae011ba in mainline.
ACPI: VIDEO: Adjust current level to closest available one.
Signed-off-by: Alexey
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Tejun Heo <[EMAIL PROTECTED]>
patch aaa092a114696f4425cd57c4d7fa05110007e247 in mainline.
sata_sis: fix SCR read breakage
SCR read for controllers which uses PCI configuration space for SCR
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Tejun Heo <[EMAIL PROTECTED]>
patch aaa092a114696f4425cd57c4d7fa05110007e247 in mainline.
sata_sis: fix SCR read breakage
SCR read for controllers which uses PCI configuration space for SCR
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Fengguang Wu <[EMAIL PROTECTED]>
patch c06a018fa5362fa9ed0768bd747c0fab26bc8849 in mainline.
This is not a new problem in 2.6.23-git17. 2.6.22/2.6.23 is buggy in the
same way.
Reiserfs
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Jeff Garzik <[EMAIL PROTECTED]>
patch 96af154710d44b574515431a0bb014888398a741 in mainline.
[libata] sata_sis: use correct S/G table size
sata_sis has the same restrictions as other SFF
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Haavard Skinnemoen <[EMAIL PROTECTED]>
patch 348badf1e825323c419dd118f65783db0f7d2ec8 in mainline.
When a DMA device is unregistered, its reference count is decremented twice
for each
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Andrew Morton <[EMAIL PROTECTED]>
patch 35d5d08a085c56f153458c3f5d8ce24123617faf in mainline.
Marin Mitov points out that delay_tsc() can misbehave if it is preempted and
rescheduled on a
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: J. Bruce Fields <[EMAIL PROTECTED]>
patch 6fa02839bf9412e18e773d04e96182b4cd0b5d57 in mainline.
As with
7fc90ec93a5eb71f4b08... "call nfsd_setuser() on fh_compose()..."
this is a
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Dan Williams <[EMAIL PROTECTED]>
patch 6c55be8b962f1bdc592d579e81fc27b11ea53dfc in mainline.
handling stripe 7629696, state=0x14 cnt=1, pd_idx=2 ops=0:0:0
check 5: state 0x6 toread
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: J. Bruce Fields <[EMAIL PROTECTED]>
patch ac8587dcb58e40dd336d99d60f852041e06cc3dd in mainline.
The v2/v3 acl code in nfsd is translating any return from fh_verify() to
nfserr_inval. This is
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Philippe Elie <[EMAIL PROTECTED]>
patch df9d177aa28d50e64bae6fbd6b263833079e3571 in mainline.
Instruction pointer returned by profile_pc() can be a random value. This
break the assumption
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Li Zefan <[EMAIL PROTECTED]>
patch 3cc2c17700c98b0af778566b0af6292b23b01430 in mainline.
The size passing to memset is wrong.
Signed-off-by Li Zefan <[EMAIL PROTECTED]>
Acked-by: Geert
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Jean Delvare <[EMAIL PROTECTED]>
patch 0f2cbd38aa377e30df3b7602abed69464d1970aa in mainline.
The sysfs interface to DMI data takes care to not make the system
serial number and UUID
2.6.23-stable review patch. If anyone has any objections, please let us know.
--
From: Jean Delvare <[EMAIL PROTECTED]>
patch be8a1f7cd4501c3b4b32543577a33aee6d2193ac in mainline.
Turns out we don't actually check the status to see if there was a
device out there to talk to,
2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Jean Delvare <[EMAIL PROTECTED]>
patch 8b925a3dd8a4d7451092cb9aa11da727ba69e0f0 in mainline.
Recent (i.e. 2005 and later) Sony Vaio laptops have names beginning
with VGN rather than PCG.
This is the start of the stable review cycle for the 2.6.23.9 release.
There are 29 patches in this series, all will be posted as a response to
this one. If anyone has any issues with these being applied, please let
us know. If anyone is a maintainer of the proper subsystem, and wants
to add a
> That's only because you're being, deliberately or accidentally, vague
> about what your actual (as opposed to imagined) requirements are.
Maybe I can help by summarizing how syslets fit in to this.
Currently the syslet patches add a single submission call which includes
an argument which is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zach Brown wrote:
> I'm sure the additional parameter will be needed, and it might be pretty
> involved. I think the current notion of syslets needs, at the very least:
All correct. I just want to point out that the proposed interface is
The following patch fixes an off by one bug in the fault reason string
reporting function, and cleans up some of the code around this buglet.
please apply.
--mgross
Signed-off-by: mark gross <[EMAIL PROTECTED]>
Index: linux-2.6.23-rc2-iommu/drivers/pci/intel-iommu.c
> Since there is no legacy interface to worry about all members added to
> the structure can and should be neutral of the word size.
OK, perhaps add a giant comment warning about that. History tells us
that people will get it wrong.
> We've done
> this with some syscalls already (like pread64)
On Tue, 2007-11-20 at 21:56 +0800, Herbert Xu wrote:
> [KERNEL]: Avoid divide in IS_ALIGN
> I was happy to discover the brand new IS_ALIGN macro and quickly
> used it in my code. To my dismay I found that the generated code
> used division to perform the test.
> This patch fixes it by changing
Ulrich Drepper wrote:
And I agree with all of the objections raised by both H. Pater Anvin
and Eric Dumazet.
Eric had no arguments and HP's comments lack a viable alternative proposal.
That's only because you're being, deliberately or accidentally, vague
about what your actual (as
Hi Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
This request is larger than I'd prefer at -rc3,
but as I wasn't available for an -rc2 merge, some things waited until now.
The good news is that the larger text changes are low risk.
The
On Tue, 20 Nov 2007 18:21:29 +0100
Jochen Friedrich <[EMAIL PROTECTED]> wrote:
> A new pid argument has been added to _tlbie for 4xx platforms.
> Add this argument to the 8xx path in mem.c, as well. As 8xx
> does not need th epid information, this argument can always be 0.
This is already fixed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zach Brown wrote:
> Have you given thought to having to perform compat translation on this?
> Today it's only copied directly from the user pointer into the union
> in the task_struct.
Since there is no legacy interface to worry about all members
> This was mentioned in one of my mails. I added the parameter to
> accommodate Linus's and Zack's idea to use the functionality for syslets
> as well. Not really a multiplexer, it is meant to be a "execute
> synchronously or asynchronously" flag. In the latter case an additional
> parameter
On Tue, Nov 20, 2007 at 06:57:55AM +0100, Ingo Molnar wrote:
>
> * Micah Dowty <[EMAIL PROTECTED]> wrote:
>
> > > this one is being triggered whenever a cpu becomes idle (schedule()
> > > --> idle_balance() --> load_balance_newidle()).
> > >
> > > (this flag is a bit #1 == 2)
> > >
> > > cat
On Tue, 20 Nov 2007 18:52:04 +0100
Thomas Renninger <[EMAIL PROTECTED]> wrote:
> Pass struct pnp_dev to pnp_clean_resource_table for cleanup reasons
Again I don't see the point of this change. A routine for cleaning up
resource tables expects logically to be passed a resource table to clean
up
> +union indirect_params {
> + struct {
> +int flags;
> + } file_flags;
> +};
Have you given thought to having to perform compat translation on this?
Today it's only copied directly from the user pointer into the union
in the task_struct.
I'd love if we could only use fixed-width fields
On Mon, Nov 19, 2007 at 04:38:02PM -0800, Andrew Morton wrote:
> On Fri, 16 Nov 2007 14:39:57 -0800
> mark gross <[EMAIL PROTECTED]> wrote:
>
> > -#define MAX_FAULT_REASON_IDX ARRAY_SIZE(fault_reason_strings) - 1
> > +#define MAX_FAULT_REASON_IDX (ARRAY_SIZE(fault_reason_strings) - 1)
David Miller wrote:
> From: Ulrich Drepper <[EMAIL PROTECTED]>
> Date: Tue, 20 Nov 2007 01:53:14 -0500
>
> FWIW, I think this indirect syscall stuff is the most ugly interface
> I've ever seen proposed for the kernel.
Well, there's no XML in /proc :) :).
But, yes, I agree that the internal code
Pass struct pnp_dev to pnp_clean_resource_table for cleanup reasons
Signed-off-by: Thomas Renninger <[EMAIL PROTECTED]>
---
drivers/pnp/manager.c | 36 ++--
1 file changed, 18 insertions(+), 18 deletions(-)
Index: linux-2.6.24-rc2-mm1/drivers/pnp/manager.c
Hi Daniel,
On Tue, Nov 20, 2007 at 11:34:20AM +0100, Daniel Reichelt wrote:
> # diff -Naur linux-2.6.23.8/fs/Kconfig linux-2.6.23.8-dhr/fs/Kconfig
> --- linux-2.6.23.8/fs/Kconfig 2007-11-16 19:14:27.0 +0100
> +++ linux-2.6.23.8-dhr/fs/Kconfig 2007-11-20 11:33:18.0 +0100
>
Unify the pnp macros to access resources in the pnp resource table
port, mem, dma and irq resource macros are now all used in the same
way. This is the basis (or makes it at least easier) for changing how
the resources are allocated for memory optimizations.
Signed-off-by: Thomas Renninger
Make use of pnp_{port,mem,irq,dma}_{start,end,flags} macros wherever possible
The macros to access the resource table in pnp sublayer was not used
consequently.
This patch makes use of these macros instead of accessing the resource
arrays directly.
For dma and irq also pnp_{dma,irq}_{start,end}
Changes:
- Introduce pnp_irq_no instead of pnp_irq_start (same for dma).
- Let irq and dma resource structs never access .end.
.end was always only a copy of .start for dma and irq
Some background what I want to do next to allocate resources on the fly:
I want to use
Jonathan McDowell sez:
> On Tue, Nov 20, 2007 at 11:35:26AM -0500, James Smart wrote:
> > The hearburn I have with these patches is that you are changing
> > driver-specific attributes, not common ones as
> > enforced/requested by a
> > subsystem. As such, you are breaking a management interface
Ingo Molnar wrote:
> cool patchset. Small nit, the series is not bisectable:
Yeah, in a few places.
Uli, this is super easy to test if you maintain the patches with guilt.
With some easy scripting around guilt push you can verify that the
series builds as each patch is applied.
- z
-
To
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Mon, 19 Nov 2007 15:20:23 -0500
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > * Dave Hansen ([EMAIL PROTECTED]) wrote:
> > > The only thing I might suggest doing differently is actually using the
> > > page_to_pfn() definition itself:
> > >
>-Original Message-
>From: Haavard Skinnemoen [mailto:[EMAIL PROTECTED]
>
>This client tests DMA memcpy using various lengths and various offsets
>into the source and destination buffers. It will initialize both
>buffers with a know pattern and verify that the DMA engine copies the
From: Cyrill Gorcunov <[EMAIL PROTECTED]>
This patch adds checking for possible NULL pointer dereference
if of_find_property() failed.
Signed-off-by: Cyrill Gorcunov <[EMAIL PROTECTED]>
---
I'm not sure about the message being printed in worst case.
Check please.
A new pid argument has been added to _tlbie for 4xx platforms.
Add this argument to the 8xx path in mem.c, as well. As 8xx
does not need th epid information, this argument can always be 0.
Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
CC arch/powerpc/mm/mem.o
arch/powerpc/mm/mem.c:
PORTA and PORTB have odr registers, as well. However, the PORTB odr
register is only 16bit.
Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
---
arch/powerpc/sysdev/commproc.c | 19 ---
1 files changed, 16 insertions(+), 3 deletions(-)
diff --git
On Tue, Nov 20, 2007 at 11:35:26AM -0500, James Smart wrote:
> The hearburn I have with these patches is that you are changing
> driver-specific attributes, not common ones as enforced/requested by a
> subsystem. As such, you are breaking a management interface for
> existing tools/scripts.
Yes,
Ian Wienand wrote:
> Hi,
>
> When rebooting today I got
>
> Will now restart.
> ACPI: PCI interrupt for device :00:03.0 disabled
> GSI 20 (level, low) -> CPU 1 (0x0100) vector 53 unregistered
> Destroying IRQ53 without calling free_irq
> WARNING: at
>
On Tue, Nov 20, 2007 at 07:05:25AM +0100, Ingo Molnar wrote:
>
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> > Greg KH wrote:
> > > Can you try applying the patch below to see if that solves the problem
> > > for you?
> > >
> >
> > I don't think this patch will help; it only has
On Tue, Nov 20, 2007 at 07:08:08AM +0100, Ingo Molnar wrote:
>
> * Chuck Ebbert <[EMAIL PROTECTED]> wrote:
>
> > On 11/17/2007 07:55 PM, Ingo Molnar wrote:
> > > * Greg KH <[EMAIL PROTECTED]> wrote:
> > >
> > >> Great, thanks for tracking this down.
> > >>
> > >> Ingo, this corrisponds to
* Rusty Russell ([EMAIL PROTECTED]) wrote:
> On Tuesday 20 November 2007 01:28:03 Mathieu Desnoyers wrote:
> > * Rusty Russell ([EMAIL PROTECTED]) wrote:
> > > I think it would be easier to just fast-path the num_online_cpus == 1
> > > case, even if you want to keep this "update_early" interface.
On Mon, Nov 19, 2007 at 05:48:00PM -0800, Joe Perches wrote:
> - printk(UM_KERN_ERR "vde_init_libstuff - vde_open_args"
> + printk(UM_KERN_ERR "vde_init_libstuff - vde_open_args "
Applied, thanks.
Jeff
--
Work email - jdike at linux dot intel dot com
-
On Mon, 2007-11-19 at 17:48 -0800, Joe Perches wrote:
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
> ---
> drivers/net/wireless/b43/phy.c |2 +-
> drivers/net/wireless/b43legacy/phy.c |2 +-
> drivers/net/wireless/bcm43xx/bcm43xx_phy.c |2 +-
>
* Borislav Petkov ([EMAIL PROTECTED]) wrote:
> On Mon, Nov 19, 2007 at 10:31:39AM -0500, Mathieu Desnoyers wrote:
> > * Borislav Petkov ([EMAIL PROTECTED]) wrote:
> > > On Fri, Nov 16, 2007 at 03:02:38PM -0500, Mathieu Desnoyers wrote:
> > > Hi,
> > > just a conventions proposal: have you thought
On Sat, 2007-11-17 at 09:12 +1100, James Morris wrote:
> On Fri, 16 Nov 2007, Eric Paris wrote:
>
> > When this protection was originally concieved it intentionally was
> > offing something even without an more 'full featured' LSM. That was the
> > whole reason I had to drop the secondary
301 - 400 of 1146 matches
Mail list logo
