On 7/1/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote:
[...]
I am heading for vacation for 20 days without Internet (real vacation :-))
I hope I'm not late in catching you here ...
By the way - kbuild.git is lacking behind on patches.
I have several queded from other peopel and have more in the
On Jun 30, 2007, at 12:42:06, Jeff Garzik wrote:
Definitely matters. Switch renegotiation can take a while, and you
must take into account the common case of interface bouncing
(immediate down, then up).
Hoards actively complained the few times we experimented with this,
because of e.g.
On 7/1/07, jim miro <[EMAIL PROTECTED]> wrote:
I am trying to get Kvm running on Debian with a custom
2.6.22-rc5 amd dual core kernel.
Custom as in custom (non-mainline) patches? Can't really
help with those, then.
To prepare I do:
/sbin/modprobe kvm-amd
FATAL: Error inserting kvm_amd
I am trying to get Kvm running on Debian with a custom
2.6.22-rc5 amd dual core kernel.
To prepare I do:
/sbin/modprobe kvm-amd
FATAL: Error inserting kvm_amd
(/lib/modules/2.6.22-rc5/extra/kvm-amd.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
dmesg returns:
kvm_amd: Unknown
On Sat, 30 Jun 2007, Kyle Moffett wrote:
> On Jun 30, 2007, at 19:57:18, Davide Libenzi wrote:
> > On Sat, 30 Jun 2007, Kyle Moffett wrote:
> > > Very simple case: SELinux is turned on, an s9 (IE: TOP_SECRET) process
> > > calls free(), and an s3 (IE: UNCLASSIFIED) process calls malloc(),
The 945 chipset used in the Z61 can only address 4GB of physical address
space and your BIOS is using some of this for PCI and other bits of
hardware. That only leaves 3GB for RAM. I believe that this restriction
is mentioned on the IBM website somewhere.
--
Matthew Garrett | [EMAIL
On Saturday 30 June 2007 03:13:24 pm Andrey Borzenkov wrote:
> After some digging, it works now :) So the story:
>
> PCMCIA includes code for checking for free IO range(s)
> code is active only if CONFIG_ISA is defined
> CONFIG_ISA has this excellent help text:
> Find out whether you
Christoph Lameter wrote:
> On Wed, 27 Jun 2007, Ethan Solomita wrote:
>
>> I looked over it at one point. Most of the code doesn't conflict, but I
>> believe that the code path which calculates the dirty limits will need
>> some merging. Doable but non-trivial.
>> -- Ethan
>
> I hope
Robert Hancock wrote:
Renato S. Yamane wrote:
Is impossible use speedstep in my Laptop with Pentium M 1,86Ghz:
#modprobe speedstep-centrino
FATAL: Error inserting speedstep_centrino
(/lib/modules/2.6.18-3-686/kernel/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.ko):
No such device
To do
Hi,
On Sat, 30 Jun 2007, Andrew Morton wrote:
> > > I continue to believe that kbuild's lets-trash-your-symlink behaviour is
> > > obnoxious, but I was unable to persuade anyone else of this.
> >
> > I thought we fixed that long time ago?!?!
>
> Nope, a simple `make oldconfig' breaks the
Hi,
On Fri, 29 Jun 2007, Andrew Morton wrote:
> > Reset generates values only if Kconfig and .config agree.
>
> unclear. Could you please explain further what this change does?
Normally generated values (Kconfig entries without a prompt) are cleared
as they are regenerated anyway and so they
On Jun 30, 2007, at 19:57:18, Davide Libenzi wrote:
On Sat, 30 Jun 2007, Kyle Moffett wrote:
Very simple case: SELinux is turned on, an s9 (IE: TOP_SECRET)
process calls free(), and an s3 (IE: UNCLASSIFIED) process calls
malloc(), getting the data from the TOP_SECRET process.
Note that
Michal Piotrowski pisze:
> Hi,
>
> Bjorn Helgaas pisze:
>> [patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
>>
>> When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
>> the device is working, but it really isn't configured correctly. The BIOS
>>
Hi,
Bjorn Helgaas pisze:
> [patch] PNP SMCf010 quirk: work around Toshiba Portege 4000 ACPI issues
>
> When we enable the SMCf010 IR device, the Toshiba Portege 4000 BIOS claims
> the device is working, but it really isn't configured correctly. The BIOS
> *will* configure it, but only if we
On Sat, 30 Jun 2007, Kyle Moffett wrote:
> On Jun 30, 2007, at 15:03:07, Davide Libenzi wrote:
> > Hmm, why would you need MAP_REUSABLE? If a page is visible at any time for a
> > given UID, and you have a login under such UID, you can fetch the content of
> > the page at any time (ie,
On Jun 30, 2007, at 15:03:07, Davide Libenzi wrote:
Hmm, why would you need MAP_REUSABLE? If a page is visible at any
time for a given UID, and you have a login under such UID, you can
fetch the content of the page at any time (ie, ptrace_attach,
gdb, ...).
Not under SELinux or other
Hi Ingo,
Ingo Molnar pisze:
> * Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
>> Subject: fix nmi_watchdog=2 bootup hang
>> References : http://lkml.org/lkml/2007/6/25/51
>> Submitter : Ingo Molnar <[EMAIL PROTECTED]>
>> Caused-By : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
>>
The Coverity checker spotted (as bug #809) that we dereference 'type'
long before we actually test it against NULL in
drivers/pnp/isapnp/core.c::isapnp_read_tag() - both branches of the
'if (tag & 0x80)' dereference type, and since this 'if' is before the test
against NULL and the return of
Andrey Borzenkov pisze:
> On Sunday 01 July 2007, Rafael J. Wysocki wrote:
>> On Saturday, 30 June 2007 06:59, Andrey Borzenkov wrote:
>>> Since 2.6.18 I do not have suspend to RAM; now I am starting to lose
>>> suspend to disk :)
>>>
>>> Environment - vanilla kernel (2.6.22-rc6 currently +
(this is back from May 16 2007, resending since it doesn't look like
the patch ever made it in anywhere)
Fix XFS memory leak; allocated transaction not freed in
xfs_inactive_free_eofblocks() in failure case.
the code allocates a transaction, but in the case where 'truncate' is
!=0 and
(this is back from May 16 2007, resending since it doesn't look like
the patch ever made it in anywhere)
The Coverity checker found a memory leak in xfs_inactive().
The offending code is this bit :
1671tp = xfs_trans_alloc(mp, XFS_TRANS_INACTIVE);
At conditional (1): "truncate !=
(originally send: Wed, 6 Jun 2007, resending since it doesn't seem to have
been picked up anywhere)
This patch adds descriptions for a number of missing files and directories
to the Documentation/00-INDEX file.
People really should learn to keep this file up-to-date when adding or
moving
(first send: Monday 25 June 2007, resending due to no response)
In drivers/isdn/capi/kcapi.c::old_capi_manufacturer(), if the call
to get_capi_ctr_by_nr(ldef.contr); in line 823 returns NULL, then
we'll be dereferencing a NULL pointer in the very next line.
(Found by Coverity checker as bug
(first send: Monday 25 June 2007, resending due to no response)
If we fail to allocate an skb in
drivers/isdn/capi/capidrv.c::send_message(), then we'll end up
dereferencing a NULL pointer.
Since out of memory conditions are not unheard of, I believe it
is better to print a error message and
On Sun, Jul 01, 2007 at 12:24:40AM +0200, Michael Buesch wrote:
> > > Hm, I was going to measure the real power advantage with a
> > > PCI-extender card. But my B44B0 card doesn't seem to work in
> > > that extender card. It works perfectly fine sticked directly into
> > > the motherboard,
On Sat, 30 Jun 2007, Arjan van de Ven wrote:
On Sat, 2007-06-30 at 16:55 +0200, Krzysztof Oledzki wrote:
Hello,
It seems that IRQ handling is somehow different between i386 and x86_64.
In my Dell PowerEdge 1950 is it possible to enable interrupts spreading
over all CPUs. This a single CPU,
On Sat, 30 Jun 2007 18:25:31 -0400 Daniel Drake <[EMAIL PROTECTED]> wrote:
> Jan Beulich wrote:
> > The code to retrieve this information was (a) inside a CONFIG_VIDEO_SELECT
> > section and (b) protected by a check of a variable (vbe_version) that
> > would get initialized only when a VESA mode
On Sat, 30 Jun 2007, Davide Libenzi wrote:
> Think about if we had this for the latest pselect/ppoll/epoll_pwait.
> Think about how your solution and mine would apply to that very much
> concrete case.
This is how all those overloaded syscalls looks like, BTW:
if (sigmask) {
On Sat, 30 Jun 2007, Ulrich Drepper wrote:
> On 6/30/07, Davide Libenzi <[EMAIL PROTECTED]> wrote:
> > But, a __get_user(), once you scrap off all the gcc wrapping, is bacially
> > a move. That could even be removed, but really I don't see the reason
> > since it allows for a cleaner strcture
Jan Beulich wrote:
The code to retrieve this information was (a) inside a CONFIG_VIDEO_SELECT
section and (b) protected by a check of a variable (vbe_version) that
would get initialized only when a VESA mode was selected on the command
line.
This patch solves a 2.6.20.11 (and 2.6.21)
On Sunday 01 July 2007 00:03:01 Lennert Buytenhek wrote:
> On Sat, Jun 30, 2007 at 11:53:25PM +0200, Michael Buesch wrote:
>
> > > When the interface is down (or driver removed), the BroadCom 44xx card
> > > remains
> > > powered on, and both its MAC and PHY is using up power.
> > > This patch
On Sat, Jun 30, 2007 at 11:53:25PM +0200, Michael Buesch wrote:
> > When the interface is down (or driver removed), the BroadCom 44xx card
> > remains
> > powered on, and both its MAC and PHY is using up power.
> > This patch makes the driver issue a MAC_CTRL_PHY_PDOWN when the interface
> > is
On 6/30/07, Davide Libenzi <[EMAIL PROTECTED]> wrote:
But, a __get_user(), once you scrap off all the gcc wrapping, is bacially
a move. That could even be removed, but really I don't see the reason
since it allows for a cleaner strcture definition in userland.
Don't generalize. The 4G/4G
On Saturday 30 June 2007 13:47:35 Török Edvin wrote:
> When the interface is down (or driver removed), the BroadCom 44xx card remains
> powered on, and both its MAC and PHY is using up power.
> This patch makes the driver issue a MAC_CTRL_PHY_PDOWN when the interface
> is halted, and does a
On Sat, 30 Jun 2007, [EMAIL PROTECTED] wrote:
>
> The downsides are that you need to save and restore the prefix flags
> across signal delivery, and you have a second user/kernel/user transition.
Both of these are basically horrible mistakes.
The first one will almost certainly break things
On Sat, 30 Jun 2007 23:10:17 +0200 Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> > I continue to believe that kbuild's lets-trash-your-symlink behaviour is
> > obnoxious, but I was unable to persuade anyone else of this.
>
> I thought we fixed that long time ago?!?!
Nope, a simple `make oldconfig'
On Sunday 01 July 2007, Rafael J. Wysocki wrote:
> On Saturday, 30 June 2007 06:59, Andrey Borzenkov wrote:
> > Since 2.6.18 I do not have suspend to RAM; now I am starting to lose
> > suspend to disk :)
> >
> > Environment - vanilla kernel (2.6.22-rc6 currently + squashfs + single
> > pata_ali
On Saturday 30 June 2007, Andrey Borzenkov wrote:
> On Saturday 30 June 2007, Bjorn Helgaas wrote:
> > This means that the SMCf010 device *did* respond, I think at the
> > FIR address 0x100. (I can't figure out the "right" way to print
> > those resource_size_t things, so I added some casts in
Ingo,
I've accidentally discovered a problem with -v18.
Some time ago, I wrote a small program to prevent my laptop from entering
low-power mode, and noticed that after upgrading my laptop's kernel from
2.4.20.9+cfs-v6 to 2.4.20.14+cfs-v18, it completely freezes if I run this
program.
The
On Fri, Jun 29, 2007 at 10:15:10PM -0700, Andrew Morton wrote:
> On Sat, 30 Jun 2007 00:17:46 -0400 [EMAIL PROTECTED] wrote:
>
> > On Fri, 29 Jun 2007 14:01:30 PDT, Andrew Morton said:
> > > On Fri, 29 Jun 2007 10:50:30 -0400
> > > [EMAIL PROTECTED] wrote:
> >
> > > > Odd - just for grins, I
Hello everyone,
A while back I asked about this on the LVM mailing list, but didn't
receive a response. Am revisiting it now, so would like a broader
audience.
I've run into some substantial read slowness when using dump or tar
to backup filesystems that are stored on LVM2 LVs. All of my tests
I was just thinking, while sys_indirect is an interesting way to add
features to a system call, the argument marshalling in user space is a
bit of a pain.
An alternate idea would be to instead have a "prefix system call" that
sets some flags that apply to the next system call made by that thread
Michal Januszewski wrote:
uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
version of vesafb and a direct successor of vesafb-tng [1].
Hi Michal,
I've just tested uvesafb on my workstation ( which has a really old
GeForce2 MX 400 Nvidia card ) and it didn't worked
On Saturday, 30 June 2007 06:59, Andrey Borzenkov wrote:
> Since 2.6.18 I do not have suspend to RAM; now I am starting to lose suspend
> to disk :)
>
> Environment - vanilla kernel (2.6.22-rc6 currently + squashfs + single
> pata_ali patch to switch off DMA on CD-ROM), single root on reiserfs,
Hi,
On Saturday, 30 June 2007 12:11, Pavel Machek wrote:
> Hi!
>
> > > > Sorry, but I can't resist the opportunity to say "Send a patch!" :)
> > > >
> > > > Seriously, though, I'd prefer not to. If we rename that acpi video
> > > > flags
> > > > variable (I assume this is what you're thinking
Charles Shannon Hendrix wrote:
Following this post is output from Linux kernel 2.6.21 showing ADMA
timeouts.
2.6.21 has improved the situation over earlier kernels, but the problems
do still occur.
nforce4 chipset, Seagate Barracuda SATA drives.
This is meant mainly as an additional
On Fri, 2007-06-29 at 21:51 +0200, Adrian Bunk wrote:
> The Coverity checker spotted the following use-after-free of "skb" in
> drivers/net/wireless/libertas/rx.c introduced by
> commit 9012b28a407511fb355f6d2176a12d4653489672 (WTF did this commit
> with the title "libertas: make debug
On Sat, 2007-06-30 at 21:24 +0200, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > Hi Ingo, this is happening in a brand new laptop, a Lenovo t61 with a
> > 7700 processor and the Santa Rosa chipset.
> >
> > Lukewarm IQ detected in hotplug locking
> > BUG: at
On Fri, 29 Jun 2007, Ulrich Drepper wrote:
> On 6/29/07, Davide Libenzi <[EMAIL PROTECTED]> wrote:
> > [include/linux/indirect.h]
> > #define SYSIND_CTX_OPENFLAGS0
> > struct sysind_ctx_OPENFLAGS {
> > __u32 ctx;
> > __u32 flags;
>
> I agree
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> Hi Ingo, this is happening in a brand new laptop, a Lenovo t61 with a
> 7700 processor and the Santa Rosa chipset.
>
> Lukewarm IQ detected in hotplug locking
> BUG: at kernel/cpu.c:44 lock_cpu_hotplug()
hm, that's an upstream kernel
* Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Subject: fix nmi_watchdog=2 bootup hang
> References : http://lkml.org/lkml/2007/6/25/51
> Submitter : Ingo Molnar <[EMAIL PROTECTED]>
> Caused-By : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> Andi Kleen <[EMAIL PROTECTED]>
>
Hi!
> > > Sorry, but I can't resist the opportunity to say "Send a patch!" :)
> > >
> > > Seriously, though, I'd prefer not to. If we rename that acpi video flags
> > > variable (I assume this is what you're thinking of), we only create cause
> > > for
> > > confusion. A variable should for
* Uwe Kleine-König <[EMAIL PROTECTED]> wrote:
> I found the problem, it had only indirectly to do with nohz. I didn't
> acknowledge the serial interrupt but as the timer and the serial need
> the same acknowledgement the serial irq got his ack always when the
> timer triggerd. Up to now
On 30 Jun 2007 14:57:06 -0400 [EMAIL PROTECTED] wrote:
> > --- a/arch/i386/kernel/cpu/mtrr/generic.c~i386-mtrr-crash-fix
> > +++ a/arch/i386/kernel/cpu/mtrr/generic.c
> > @@ -65,7 +65,8 @@ get_fixed_ranges(mtrr_type * frs)
> >
> > void mtrr_save_fixed_ranges(void *info)
> > {
> > -
Andrew Morton wrote:
> On Fri, 29 Jun 2007 14:32:09 +0200
> Mariusz Kozlowski <[EMAIL PROTECTED]> wrote:
>> anyway after unselecting XMON we can see:
>>
>> CC [M] fs/xfs/linux-2.6/xfs_ioctl32.o
>> fs/xfs/linux-2.6/xfs_ioctl32.c: In function 'xfs_ioc_bulkstat_compat':
>>
On Fri, 29 Jun 2007, Kyle Moffett wrote:
> Well I would be very interested in actually being able to use this feature
> under SELinux, I think that just the underlying "can-I-use-this-page" logic
> needs modification. Maybe "MAP_REUSABLE"? That would both imply that we can
> accept reused (IE:
Responding to various proposed fixes:
> Index: linux/arch/i386/kernel/cpu/mtrr/main.c
> ===
> --- linux.orig/arch/i386/kernel/cpu/mtrr/main.c
> +++ linux/arch/i386/kernel/cpu/mtrr/main.c
> @@ -734,8 +734,11 @@ void mtrr_ap_init(void)
On Saturday 30 June 2007 08:02:16 Joerg Schilling wrote:
> Willy Tarreau <[EMAIL PROTECTED]> wrote:
> > Jörg,
> >
> > On Thu, Jun 28, 2007 at 12:39:57PM +0200, Joerg Schilling wrote:
> > > David Woodhouse <[EMAIL PROTECTED]> wrote:
> > > > On Thu, 2007-06-28 at 12:27 +0200, Joerg Schilling wrote:
Muli Ben-Yehuda <[EMAIL PROTECTED]> writes:
>
> The convention is to print a KERN_DEBUG message if hardware is not
> found when probing it, otherwise the boot messages become cluttered
> with lots of "$FOO not found".
No the convention is to print no message at all when nothing is found
Some
Muli Ben-Yehuda <[EMAIL PROTECTED]> wrote:
>
>> And probably some similar mechanism for network drivers that limits
>> MTUs.
>
> Will that guarantee that block and net IOs will not straddle a page
> boundary?
Mostly. There is the thorny case of slab debugging that breaks
these nice assumptions.
Following this post is output from Linux kernel 2.6.21 showing ADMA timeouts.
2.6.21 has improved the situation over earlier kernels, but the problems do
still occur.
nforce4 chipset, Seagate Barracuda SATA drives.
This is meant mainly as an additional data point in case it helps someone
On Tue, 19 Jun 2007 18:32:34 +0200
Nicolas Ferre <[EMAIL PROTECTED]> wrote:
>
> Typo fix in at91_mci driver : standardized the typo
> (at91_mci everywhere)
>
> Signed-off-by: Nicolas Ferre <[EMAIL PROTECTED]>
> ---
Thanks, applied.
signature.asc
Description: PGP signature
On Sat, 30 Jun 2007, Jeff Garzik wrote:
> Like SATA, we actually want to support BOTH -- active hotplug and PHY
> power-down -- and so this wanders into power management policy.
>
> Give me a knob, and we can program plenty of ethernet|SATA|USB|... drivers
> to power down the PHY and save power.
Frank Fiene wrote:
On Samstag, 30. Juni 2007, Robert Hancock wrote:
Frank Fiene wrote:
Lenovo Z61p, Intel Core2 Duo T7200
I have 4GB RAM installed and BIOS recognize 4GB RAM.
Linux kernel (Ubuntu-7.04, 32bit-PAE and 64bit, openSUSE-10.2
32bit-PAE and 64bit) tells me: only 3GB of RAM are
On Fri, 29 Jun 2007, Dmitry Torokhov wrote:
> Finally gottent to the patch. It seems a little long-winded, how about
> the patch below instead?
Well, your version of the patch:
1. does not make it clear to *userland* that using EV_SCAN instead of EV_KEY
is something that is not to be done. If
On Sat, 30 Jun 2007 12:42:06 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Arjan van de Ven wrote:
> > Matthew Garrett wrote:
> >> Do you still get link beat detection when the phy is powered down?
>
> > does that matter?
> > If the interface is down, nic drivers aren't expected to detect
On Samstag, 30. Juni 2007, Robert Hancock wrote:
> Frank Fiene wrote:
> > Lenovo Z61p, Intel Core2 Duo T7200
> >
> > I have 4GB RAM installed and BIOS recognize 4GB RAM.
> > Linux kernel (Ubuntu-7.04, 32bit-PAE and 64bit, openSUSE-10.2
> > 32bit-PAE and 64bit) tells me: only 3GB of RAM are
On Sat, Jun 30, 2007 at 09:32:05AM -0700, Andrew Morton wrote:
>[..]
>
> > Given a set of historical modifiers of a file,
> > would you take the most common commiter(s), or the most common
> > _recent_ commiter(s), or what? It's a bit fuzzy.
>
> All the above? Multiply frequency by recency,
On Sat, Jun 30, 2007 at 09:32:05AM -0700, Andrew Morton wrote:
> On Sat, 30 Jun 2007 13:47:52 +0300 Dan Aloni <[EMAIL PROTECTED]> wrote:
>
> > On Sat, Jun 30, 2007 at 02:54:25AM -0700, Andrew Morton wrote:
> > > On Fri, 29 Jun 2007 19:51:53 -0700 "Kok, Auke" <[EMAIL PROTECTED]> wrote:
> > >
> >
On Fri, Jun 29, 2007 at 05:40:52PM +0100, David Woodhouse wrote:
>
> Remember you have to support _both_ 32-bit and 64-bit system calls. You
> need to define struct compat_pps_info and struct compat_pps_params, and
> you'll have to provide a compat wrapper for sys_time_pps_getparams() and
>
On Sat, Jun 30, 2007 at 09:38:27AM +0100, Christoph Hellwig wrote:
>
> Sorry for coming in that late, but using syscalls for something as
> periphal sounds like a very bad idea to me, and the syscalls aren't
> defined nicely either (e.g. you have an ioctl lookalike). I'd say
> back to the
Arjan van de Ven wrote:
Matthew Garrett wrote:
Do you still get link beat detection when the phy is powered down?
does that matter?
If the interface is down, nic drivers aren't expected to detect link...
if userspace wants to find link status it should have the interface up.
Definitely
On Tue, Jun 26, 2007 at 11:42:41AM +0100, Jonathan McDowell wrote:
> Have you considered using libx86[1] in v86d? It looks very similar to
> what you have at present and there are plans to extend it to non
> x86(_64) archs.
It looks like an interesting solution and it is indeed similar to what
Documentation for the uvesafb driver.
Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]>
---
Documentation/fb/uvesafb.txt | 187 ++
1 files changed, 187 insertions(+), 0 deletions(-)
diff --git a/Documentation/fb/uvesafb.txt
Change the maximum message size to 4k to allow transfers of VBE
data blocks from userspace.
Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]>
---
include/linux/connector.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/connector.h
On Sat, 30 Jun 2007 13:47:52 +0300 Dan Aloni <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 30, 2007 at 02:54:25AM -0700, Andrew Morton wrote:
> > On Fri, 29 Jun 2007 19:51:53 -0700 "Kok, Auke" <[EMAIL PROTECTED]> wrote:
> >
> > > > Some extensions to the popular E-Mail clients might be needed
> > >
Add connector idx and val constants for v86d and uvesafb.
Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]>
---
include/linux/connector.h |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/connector.h b/include/linux/connector.h
index 10eb56b..14cecaf
Make fb_destroy_modelist an exported symbol for use in the uvesafb driver.
Signed-off-by: Michal Januszewski <[EMAIL PROTECTED]>
---
drivers/video/modedb.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/video/modedb.c b/drivers/video/modedb.c
index
uvesafb is a generic driver for VBE2+ compliant video cards; an enhanced
version of vesafb and a direct successor of vesafb-tng [1].
This is the second version of this patch, and it incorporates all fixes
and cleanups suggested on the lkml. My thanks to everyone who took
their time to review the
Andrew Morton wrote:
All my .configs have mouldered since I lost the ability to have .config be
a symlink to a revision-controlled file (used to carry a custom patch for
this, but it died).
I continue to believe that kbuild's lets-trash-your-symlink behaviour is
obnoxious, but I was unable to
On Saturday 30 June 2007 11:13, Christoph Hellwig wrote:
> We need something like this, but I don't quite like the way you've done
> it. First the name is wrong, it's not a nameidata anymore but a lookup
> intent, so it should be named that way, struct lookup_intent.
Sure, that name was pretty
On Sat, Jun 30, 2007 at 04:19:23PM +0100, Matthew Garrett wrote:
> I'd agree that there's a need for a state where we power down as much as
> possible (even at the cost of functionality), but where possible it
> would also be nice to offer a state where the mac is powered down and
> the phy
On Sat, 2007-06-30 at 16:55 +0200, Krzysztof Oledzki wrote:
> Hello,
>
> It seems that IRQ handling is somehow different between i386 and x86_64.
>
> In my Dell PowerEdge 1950 is it possible to enable interrupts spreading
> over all CPUs. This a single CPU, four CORE system (Quad-Core E5335
On Sat, Jun 30, 2007 at 07:44:59AM -0700, Arjan van de Ven wrote:
> Matthew Garrett wrote:
> >Do you still get link beat detection when the phy is powered down?
> >
> does that matter?
> If the interface is down, nic drivers aren't expected to detect
> link... if userspace wants to find link
[EMAIL PROTECTED] wrote:
> > "Christoph" == Christoph Hellwig <[EMAIL PROTECTED]> writes:
>
> Christoph> On Tue, Jun 26, 2007 at 10:07:24AM -0700, Jared Hulbert
>
> Christoph> wrote:
> >> If you have a large array of a non-volatile semi-writeable memory
> >> such as a highspeed NOR Flash or
On Saturday 30 June 2007, Bjorn Helgaas wrote:
> This means that the SMCf010 device *did* respond, I think at the
> FIR address 0x100. (I can't figure out the "right" way to print
> those resource_size_t things, so I added some casts in the appended
> patch.)
>
Those can be 64 bit if
Matthew Garrett wrote:
On Sat, Jun 30, 2007 at 02:47:35PM +0300, Török Edvin wrote:
When the interface is down (or driver removed), the BroadCom 44xx card
remains
powered on, and both its MAC and PHY is using up power.
This patch makes the driver issue a MAC_CTRL_PHY_PDOWN when the interface
Hi,
added this pci id to support my:
lspci:
01:00.0 RAID bus controller: Adaptec Unknown device 0243 (rev 02)
lspci -n:
01:00.0 0104: 9005:0243 (rev 02)
seems to work fine.
florian attenberger
--- 2.6.22-rc6/drivers/ata/sata_mv.c2007-06-30 16:21:47.462020256 +0200
+++
John Keller wrote:
[adding Andi Kleen]
John Keller wrote:
Place all the IOACPI NMI support code under CONFIG_ACPI
to clear up build errors with certain configs.
Signed-off-by: John Keller <[EMAIL PROTECTED]>
---
Is there some architectural reason that IO APIC NMI support should
require ACPI?
On Fri, 29 Jun 2007, Martin Schwidefsky wrote:
> On Fri, 2007-06-29 at 19:56 +0100, Hugh Dickins wrote:
> > I don't dare comment on your page_mkclean_one patch (5/5),
> > that dirty page business has grown too subtle for me.
>
> Oh yes, the dirty handling is tricky. I had to fix a really nasty
[EMAIL PROTECTED] (Joerg Schilling) writes:
> Willy Tarreau <[EMAIL PROTECTED]> wrote:
>
>> Jörg,
>>
>> On Thu, Jun 28, 2007 at 12:39:57PM +0200, Joerg Schilling wrote:
>> > David Woodhouse <[EMAIL PROTECTED]> wrote:
>> >
>> > > On Thu, 2007-06-28 at 12:27 +0200, Joerg Schilling wrote:
>> > > >
[ Trimmed Cc: list ]
On 6/30/07, Steve French <[EMAIL PROTECTED]> wrote:
The reason that cifs switched from wait_for_completion to the kthread
call to cifs_demultiplex_thread in the first place is because without
use of kthread it won't work with a linux-vserver. See the thread:
Andrew Morton wrote:
On Fri, 29 Jun 2007 19:51:53 -0700 "Kok, Auke" <[EMAIL PROTECTED]> wrote:
Some extensions to the popular E-Mail clients might be needed
here. Also, a bot reading LKML would automatically send links
about posted patches to the other mailing lists whenever
someone forgets
On Thursday 28 June 2007, Andrew Morton wrote:
> > +#undef DISABLE_TEST_MODE
>
> enabling DISABLE_TEST_MODE seens to enable test mode. Confused.
Blame it on Intel. ISTR that early pxa2[156]x silicon had
something called "test mode". And a boatload of errata, with
a common thread in
>
> [adding Andi Kleen]
>
> John Keller wrote:
> > Place all the IOACPI NMI support code under CONFIG_ACPI
> > to clear up build errors with certain configs.
> >
> > Signed-off-by: John Keller <[EMAIL PROTECTED]>
> > ---
>
> Is there some architectural reason that IO APIC NMI support should
>
On Friday 29 June 2007, Dmitry Krivoschekov wrote:
> David Brownell wrote:
> > On Thursday 28 June 2007, Rodolfo Giometti wrote:
> >
> >> As suggest by Leo let me propose to you my new patch for PXA27x UDC
> >> support.
> >>
> >> Please, let me know what I have to do for kernel inclusion. :)
> >
>
On Friday 29 June 2007, Rodolfo Giometti wrote:
> On Thu, Jun 28, 2007 at 02:53:22PM -0700, David Brownell wrote:
> >
> > Let's start with *JUST* a driver, not trying to update everything
> > else in the USB Gadget stack so that it looks like it's designed
> > specifically to handle all of
On Sat, 2007-06-30 at 19:50 +0530, Satyam Sharma wrote:
> Hi,
> Right, as Mike just said, these warnings are the ones from
> drivers/video/pvr2fb.c which the patch didn't touch ... that was only
> to get rid of the "(between 'mv_dreamcast' and 'systemasic_int')"
> warning. But of course, we can't
Willy Tarreau <[EMAIL PROTECTED]> wrote:
>
> > Jörg
> [advertisements removed]
Please stop this kind of trolling, you did not remove anything here,
so do not claim to remove things
As you don't seem to know the nettiquette:
If you believe you have some kind of problems that was used by
Hi,
On 6/30/07, Adrian McMenamin <[EMAIL PROTECTED]> wrote:
[...]
WARNING: drivers/built-in.o(.text+0x168e0): Section mismatch: reference
to .init.data: (between 'pvr2fb_check_var' and 'pvr2fb_interrupt')
WARNING: drivers/built-in.o(.text+0x1701c): Section mismatch: reference
to .init.data:
1 - 100 of 336 matches
Mail list logo
