On Tue, 19 Jun 2007, Alexandre Oliva wrote:
On Jun 19, 2007, [EMAIL PROTECTED] wrote:
On Tue, 19 Jun 2007, Alexandre Oliva wrote:
Once again, now with clearer starting conditions (not intended to
match TiVo in any way, BTW; don't get into that distraction)
Vendor doesn't care about
Fix compile error:
In file included from drivers/infiniband/core/addr.c:32:
include/linux/inetdevice.h:15: error: '__NET_IPV4_CONF_MAX' undeclared here
(not in a function)
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
include/linux/inetdevice.h |1 +
1 files changed, 1
Fix several build errors with PCMCIA=m && NET_PCMCIA=y:
LD .tmp_vmlinux1
drivers/built-in.o: In function `nmclan_release':
nmclan_cs.c:(.text+0x14026c): undefined reference to `pcmcia_disable_device'
...
drivers/built-in.o: In function `exit_xirc2ps_cs':
Avoid compile warning if !ACPI_BLACKLIST_YEAR
CC drivers/acpi/blacklist.o
drivers/acpi/blacklist.c:76:5: warning: "CONFIG_ACPI_BLACKLIST_YEAR" is not
defined
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/blacklist.c |2 +-
1 files changed, 1 insertions(+), 1
Fix build error if ACPI && !ACPI_SYSTEM as
bus.c depended on event.c
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/bus.c |2 +-
drivers/acpi/event.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
Fix compile error with ACPI && !ACPI_POWER as bus.c
depends on power.c
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/Kconfig |4
drivers/acpi/Makefile |2 +-
2 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/Kconfig
Fix kernel build problem as MSI_LAPTOP depends on ACPI_EC.
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/misc/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 72774c9..0d6f369 100644
---
On Jun 19, 2007, "Dave Neuer" <[EMAIL PROTECTED]> wrote:
> On 6/19/07, Alexandre Oliva <[EMAIL PROTECTED]> wrote:
>> But it takes only a small fraction of the tivoizers to decide to take
>> out the locks, when faced with the costs mentioned above, for us to
>> gain contributions from even a small
Fix kernel build problem:
thinkpad_acpi.c:(.text+0x7486a): undefined reference to `ec_write'
(as THINKPAD_ACPI depends on ACPI_EC)
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/misc/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Fix Kconfig build warning:
scripts/kconfig/mconf arch/x86_64/Kconfig
drivers/input/keyboard/Kconfig:170:warning: 'select' used by config symbol
'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
drivers/input/mouse/Kconfig:182:warning: 'select' used by config symbol
'MOUSE_ATARI'
This is a series of minor fixes for problems observed while
doing some randconfig fun on x86_64.
Some problems might have been reported on LKML before. But AFAIK they
are not fixed in current git. Thus I report them again - including
possible fixes.
Regards,
Andreas
--
Operating | AMD Saxony
On Jun 19, 2007, [EMAIL PROTECTED] wrote:
> On Tue, 19 Jun 2007, Alexandre Oliva wrote:
>>
>> Once again, now with clearer starting conditions (not intended to
>> match TiVo in any way, BTW; don't get into that distraction)
>>
>>
>> Vendor doesn't care about tivoizing, their business works the
On Tue, 19 Jun 2007 15:38:01 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> Ok and BUILD_BUG_ON really works? Had some bad experiences with it.
hm, I don't recall any problems, apart from its very obscure error
reporting.
But if it breaks, we get an opportunity to fix it ;)
-
To
> > You keep smuggling in the same assumption without ever
> > defending it. There
> > is a user. There is a person who gets to decide what software runs on a
> > particular piece of hardware. You keep assuming they must be the same
> > person.
> No, I'm just saying that whoever gets to decide
On Tue, 19 Jun 2007, Andrew Morton wrote:
> On Tue, 19 Jun 2007 15:22:36 -0700 (PDT)
> Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 19 Jun 2007, Andrew Morton wrote:
> >
> > > On Mon, 18 Jun 2007 02:58:48 -0700
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > +
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Tue, 19 Jun 2007 12:33:16 -0700
> Only x86_64 and ia64 are fixed. Would it be correct to assume that the
> other CONFIG_COMPAT architectures also need to be fixed?
Only platforms which compat to "i386" have the issue wrt.
the alignment of "u64"
On Tue, 19 Jun 2007, Matt Mackall wrote:
> I worry a bit about adding another branch checking __GFP_ZERO in such
> a hot path for SLAB/SLUB.
Its checking the gfpflags variable on the stack. In a recently touched
cachline.
-
To unsubscribe from this list: send the line "unsubscribe
On Tue, 19 Jun 2007, Pekka Enberg wrote:
> On 6/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > We use the parameter formerly used by the destructor to pass an optional
> > pointer to a kmem_cache_ops structure to kmem_cache_create.
> >
> > kmem_cache_ops is created as empty. Later
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Tue, 19 Jun 2007 12:04:33 -0700 (PDT)
>
>
> On Tue, 19 Jun 2007, John Stoffel wrote:
> >
> > Shouldn't the vm_dirty_ratio be based on the speed of the device, and
> > not the size of memory?
>
> Yes. It should depend on:
> - speed of the
On Tue, 19 Jun 2007, Lee Schermerhorn wrote:
> > - File / Socket. One may have particular reasons to place
> > objects on a set of nodes because of how the threads of
> > an application are spread out in the system.
>
> ...how the tasks/threads are spread out and how the application accesses
> > MAINTAINERS says riscom8 is orphaned so not sure
> > if anybody cares. Spotted this when playing with modprobe
> > walking /lib/modules/`uname -r`/kernel in a loop ;)
>
> Oh wow.
>
> I wonder why it does that. The code literally does:
>
> save_flags(flags);
> cli();
>
On Tue, 19 Jun 2007 15:22:36 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Jun 2007, Andrew Morton wrote:
>
> > On Mon, 18 Jun 2007 02:58:48 -0700
> > [EMAIL PROTECTED] wrote:
> >
> > > + BUG_ON(KMALLOC_MIN_SIZE > 256 ||
> > > + (KMALLOC_MIN_SIZE &
On Wed, 20 Jun 2007 00:59:26 +0900 (JST)
Atsushi Nemoto <[EMAIL PROTECTED]> wrote:
>
> This driver supports M41T80, M41T81 and M41ST85. The old m41t00
> driver supports M41T00, M41T81 and M41T85(M41ST85). While the M41T00
> chip is now supported by rtc-ds1307 driver, this driver does not
>
Quoting Mimi Zohar ([EMAIL PROTECTED]):
> This is a re-release of Integrity Based Access Control(IBAC) LSM module
> which bases access control decisions on the new integrity framework
> services. IBAC is a sample LSM module to help clarify the interaction
> between LSM and Linux Integrity
On Tue, Jun 19, 2007 at 03:07:40PM -0700, [EMAIL PROTECTED] wrote:
> since anything starting with . is considered a 'hidden' file per *nix
> tradition it's ignored by many programs and optionally ignored by most
> others (and anything that doesn't ignore . files when presending files to
> the
On Tue, 19 Jun 2007, Andrew Morton wrote:
> On Mon, 18 Jun 2007 02:58:48 -0700
> [EMAIL PROTECTED] wrote:
>
> > + BUG_ON(KMALLOC_MIN_SIZE > 256 ||
> > + (KMALLOC_MIN_SIZE & (KMALLOC_MIN_SIZE - 1)));
>
> BUILD_BUG_ON?
>
Does not matter. That code is __init.
-
To unsubscribe from
This config option (DMAR_FLPY_WA) sets up 1:1 mapping for the
floppy device so that the floppy device which does not use
DMA api's will continue to work.
Once the floppy driver starts using DMA api's this config option
can be turn off or this patch can be yanked out of kernel at that
MSI interrupt handler registrations and fault handling support
for Intel-IOMMU hadrware.
This patch enables the MSI interrupts for the DMA remapping units
and in the interrupt handler read the fault cause and outputs the
same on to the console.
Signed-off-by: Anil S Keshavamurthy <[EMAIL
This code implements a generic IOVA allocation and
management. As per Dave's suggestion we are now allocating
IO virtual address from Higher DMA limit address rather
than lower end address and this eliminated the need to preserve
the IO virtual address for multiple devices sharing the
When we fix all the opensource gfx drivers to use the DMA api's,
at that time we can yank this config options out.
Signed-off-by: Anil S Keshavamurthy <[EMAIL PROTECTED]>
---
Documentation/Intel-IOMMU.txt |5 +
arch/x86_64/Kconfig | 11 +++
arch/x86_64/kernel/e820.c
Introduce intel_iommu=forcedac commandline option.
This option is helpful to verify the pci device capability
of handling physical dma'able address greater than 4G.
Signed-off-by: Anil S Keshavamurthy <[EMAIL PROTECTED]>
---
Documentation/kernel-parameters.txt |7 +++
Introduce the size param for clflush_cache_range().
Signed-off-by: Anil S Keshavamurthy <[EMAIL PROTECTED]>
---
arch/x86_64/mm/pageattr.c |6 +++---
include/asm-x86_64/cacheflush.h |1 +
2 files changed, 4 insertions(+), 3 deletions(-)
Index:
Intel IOMMU driver needs memory during DMA map calls to setup its internal
page tables and for other data structures. As we all know that these DMA
map calls are mostly called in the interrupt context or with the spinlock
held by the upper level drivers(network/storage drivers), so in order to
This patch adds support for early detection and parsing of DMAR's
(DMA Remapping ) reported to OS via ACPI tables.
DMA remapping(DMAR) devices support enables independent address
translations for Direct Memory Access(DMA) from Devices.
These DMA remapping devices are reported via ACPI tables
and
When devices are under a p2p bridge, upstream
transactions get replaced by the device id of the bridge as it owns the
PCIE transaction. Hence its necessary to setup translations on behalf of the
bridge as well. Due to this limitation all devices under a p2p share the same
domain in a DMAR.
We
Hi All,
This patch supports the upcomming Intel IOMMU hardware
a.k.a. Intel(R) Virtualization Technology for Directed I/O
Architecture and the hardware spec for the same can be found here
http://www.intel.com/technology/virtualization/index.htm
This version of the patches
Maybe this is the correct fix:
WARNING: drivers/built-in.o(.text+0x8742a): Section mismatch: reference to
.init.data:chipsfb_fix (between 'chipsfb_pci_init' and 'chipsfb_set_par')
WARNING: drivers/built-in.o(.text+0x87432): Section mismatch: reference to
.init.data:chipsfb_fix (between
[EMAIL PROTECTED] wrote:
>
> the only trouble I ever had with the .snapshot approach is when tar or
> find would decend down into the .snapshot when I didn't really intend
> for it to do so.
>
Netapp optionally made .snapshot not show up in readdir, which solved
that problem.
I have a bigger
On Tue, Jun 19, 2007 at 01:49:30PM -0700, Darrick J. Wong wrote:
>
> This fixes the problem! Hurrah!
Great! Andrew, please include the appended patch in -mm.
Subject: [patch] x86_64, irq: use mask/unmask and proper locking in fixup_irqs
From: Suresh Siddha <[EMAIL PROTECTED]>
Force irq
Am Dienstag 19 Juni 2007 20:32 schrieb Alexandre Oliva:
> On Jun 19, 2007, Hans-Jürgen Koch <[EMAIL PROTECTED]> wrote:
>
> > Am Dienstag 19 Juni 2007 04:46 schrieb Alexandre Oliva:
> >> The distrust for the FSF led to this very short-sighted decision of
> >> painting the Linux community into a
Alan Cox wrote:
>
> Yes but tdskb:foo.mac[1013,1013,frob];4 is *not* elegant.
I think describing VMS pathname syntax as "not elegant" is kind of like
describing George W. Bush as "not a genius."
> POSIX is very
> clear about what is acceptable as magic in a pathname, and the unix spec
> even
On Tue, 19 Jun 2007, Lennart Sorensen wrote:
On Tue, Jun 19, 2007 at 02:03:07PM -0400, Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method that
uses legal path character, but doesn't break anything. With this method,
userspace tools will have to be taught
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Tue, 19 Jun 2007 13:52:14 -0400
> Stephen Hemminger wrote:
> > On Wed, 13 Jun 2007 21:36:30 -0700
> > Jay Vosburgh <[EMAIL PROTECTED]> wrote:
> >
> >>The following patch (based on a patch from Stephen Hemminger
> >> <[EMAIL PROTECTED]>) removes use
On Tue, Jun 19, 2007 at 09:39:03PM +0200, Ingo Molnar wrote:
>
> 2.6.22 must-have item - perhaps suitable for -stable too, because it was
> reproduced on 2.6.21.5 too.
>
> -->
> From: Christoph Lameter <[EMAIL PROTECTED]>
> Subject: [patch] sched: fix next_interval
On Jun 19, 2007, "David Schwartz" <[EMAIL PROTECTED]> wrote:
>> Right. All GPL can say is that you cannot impose further restrictions
>> on how the user adapts the software, and since the user runs the
>> software on that computer, that means you must not restrict the user's
>> ability to
Am Dienstag 19 Juni 2007 13:50 schrieb Michael Poole:
> Hans-Jürgen Koch writes:
>
> > No. Credible licenses should be simple like physical laws. Newton's law
> > is expressed in terms of a single mathematical equation. That's why it's
> > still valid, and you still learn it at school although
On Tue, 19 Jun 2007, Mariusz Kozlowski wrote:
>
> MAINTAINERS says riscom8 is orphaned so not sure
> if anybody cares. Spotted this when playing with modprobe
> walking /lib/modules/`uname -r`/kernel in a loop ;)
Oh wow.
I wonder why it does that. The code literally does:
On Jun 19, 2007, [EMAIL PROTECTED] wrote:
> On Tue, 19 Jun 2007, Alexandre Oliva wrote:
>> On Jun 19, 2007, Daniel Drake <[EMAIL PROTECTED]> wrote:
>>
>>> I realise that the latest GPLv3 draft would not pose restrictions
>>> here, as such devices would not be classified as consumer
>>> products.
On 19 Jun, Chris Wright wrote:
> * Stefan Richter ([EMAIL PROTECTED]) wrote:
>> + Other kernel trees can be found listed at http://kernel.org/git and in
>
> Should be http://git.kernel.org/ these days
Right.
From: Stefan Richter <[EMAIL PROTECTED]>
Subject: Documentation/HOWTO: update URLs of
On Tue, 19 Jun 2007 12:08:52 -0700
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
> Chris Snook wrote:
> > I pointed out NetApp's .snapshot directories because that's a method
> > that uses legal path character, but doesn't break anything. With this
> > method, userspace tools will have to be
On Tue, 19 Jun 2007, Alexandre Oliva wrote:
On Jun 19, 2007, [EMAIL PROTECTED] wrote:
based on my experiance looking at the software released for tivos, I
think you are over-estimating these numbers. if there are more then a
dozen people producing things that are good enough to be useful and
Joshua David Williams wrote:
I've been keeping tabs on the GPLv3 dispute for quite some time. It seems to
me that the best solution would be for us to write our own open source
license - one that would be written specifically to uphold the ten rights in
the open source definition.
Your
Hello,
MAINTAINERS says riscom8 is orphaned so not sure
if anybody cares. Spotted this when playing with modprobe
walking /lib/modules/`uname -r`/kernel in a loop ;)
BUG: sleeping function called from invalid context at kernel/mutex.c:86
in_atomic():0, irqs_disabled():1
[]
On Tue, 2007-06-19 at 13:57 -0700, Daniel Walker wrote:
> Looks like you have a whitespace issue here.. Should be tabs, not
> spaces.
Bah, there's a "/* -*- linux-c -*- " at the top of that file that's
messing up with my emacs!
Is this better :-p
Signed-off-by: Steven Rostedt <[EMAIL
Thanks for pointing this out. It seems that we would need to allocate
this extra byte somewhere in kernel ppp code.
However, I am not very familiar with that part of the code yet, and
I'll appreciate any help with finding parts of code where obuffer for
mppe_decompress is allocated.
On 6/20/07,
On Tue, 19 Jun 2007, Thomas Renninger wrote:
> On Sun, 2007-06-17 at 19:49 -0300, Henrique de Moraes Holschuh wrote:
> > On Sun, 17 Jun 2007, Thomas Renninger wrote:
> > > Create __mod_acpi_device_table symbol for all acpi drivers.
> >
> > thinkpad-acpi will autoload by DMI ids in 2.6.23, which
Hi Nigel,
On Tuesday, 19 June 2007 13:18, Nigel Cunningham wrote:
> Hi all
>
> Here's what I have after today's work.
>
> I haven't yet been able to test on x86, but can confirm that it works okay on
> x86_64. I'm currently working towards testing it on my old Omnibook. My P4
> desktop won't
On 6/19/07, Alexandre Oliva <[EMAIL PROTECTED]> wrote:
On Jun 19, 2007, Anders Larsen <[EMAIL PROTECTED]> wrote:
> Only, your statement above seems to run counter to your previous claims
> that the "anti-tivoisation" provisions of GPLv3 would bring _more_
> developers to copyleft software.
>
> The current memory policy APIs can work in such a "containerized"
> environment if we can reconcile the policy APIs' notion of nodes with
> the set of nodes that container allows. Perhaps we need to revisit the
> "cpumemset" proposal that provides a separate node id namespace in each
>
On Jun 19, 2007, Jan Harkes <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 19, 2007 at 02:40:59AM -0300, Alexandre Oliva wrote:
>> > The actual software is mailed to you on a credit card sized
>> > ROM when you activate service.
> ...
>> The GPLv3 won't remove every way in which people who want/need to
On Tue, 19 Jun 2007, Alexandre Oliva wrote:
Once again, now with clearer starting conditions (not intended to
match TiVo in any way, BTW; don't get into that distraction)
Vendor doesn't care about tivoizing, their business works the same
either way.
Vendor's employees will contribute the
* Stefan Richter ([EMAIL PROTECTED]) wrote:
> + Other kernel trees can be found listed at http://kernel.org/git and in
Should be http://git.kernel.org/ these days
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Hi Christoph x 2,
On Tue, 19 Jun 2007, Christoph Hellwig wrote:
> Hmm, I must have missed the macro going in. Frankly speaking I plain hate
> it. It's a rather useless obsfucation.
I hate the name, but the macro is far from useless.
On 6/19/07, Christoph Lameter <[EMAIL PROTECTED]> wrote:
On Jun 19, 2007, Anders Larsen <[EMAIL PROTECTED]> wrote:
> Only, your statement above seems to run counter to your previous claims
> that the "anti-tivoisation" provisions of GPLv3 would bring _more_
> developers to copyleft software.
> So which one is it?
We might lose your contributions,
On Jun 19, 2007, [EMAIL PROTECTED] wrote:
> based on my experiance looking at the software released for tivos, I
> think you are over-estimating these numbers. if there are more then a
> dozen people producing things that are good enough to be useful and
> releasing their results as opensource
On Tue, Jun 19, 2007 at 08:51:25PM +0200, Karel Zak wrote:
> > > I don't think that mtab is a good place for this shared subtree
> > > stuff. The mtab needs to die.
> >
> > Perhaps. Perhaps not.
> >
> > On the one hand I think there is a place for arbitrary user-space info
> > about mounted
On Tue, 19 Jun 2007, Alexandre Oliva wrote:
On Jun 19, 2007, Daniel Drake <[EMAIL PROTECTED]> wrote:
I realise that the latest GPLv3 draft would not pose restrictions
here, as such devices would not be classified as consumer
products.
And even if they were, there's always ROM.
I don't know
On Mon, Jun 18, 2007 at 02:58:43AM -0700, [EMAIL PROTECTED] wrote:
> It becomes now easy to support the zeroing allocs with generic inline
> functions
> in slab.h. Provide inline definitions to allow the continued use of
> kzalloc, kmem_cache_zalloc etc but remove other definitions of zeroing
>
Matthew> On Tue, Jun 19, 2007 at 04:34:42PM -0400, John Stoffel wrote:
>> > "Jack" == Jack Stone <[EMAIL PROTECTED]> writes:
>>
Jack> The whole idea of the file system is that it wouldn't return the
Jack> file in the file listing. The user would have to know that the
Jack> file system was
On Tue, 2007-06-19 at 16:17 -0400, Steven Rostedt wrote:
> The show all regs sysrq uses the nmi function to do it. But this
> function expects preemption to be off, or funny things happen.
>
> Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
>
> Index: linux-2.6.21-rt9/drivers/char/sysrq.c
>
On 6/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
We use the parameter formerly used by the destructor to pass an optional
pointer to a kmem_cache_ops structure to kmem_cache_create.
kmem_cache_ops is created as empty. Later patches populate kmem_cache_ops.
I like kmem_cache_ops but I
On 6/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
kmalloc_node() and kmem_cache_alloc_node() were not available in
a zeroing variant in the past. But with __GFP_ZERO it is possible
now to do zeroing while allocating.
Looks good. Maybe we want to phase out the zeroing variants altogether
On Tue, 19 Jun 2007, Lennart Sorensen wrote:
On Mon, Jun 18, 2007 at 02:56:10PM -0700, [EMAIL PROTECTED] wrote:
yes, I'm useing promise drive shelves, I have them configured to export
the 15 drives as 15 LUNs on a single ID.
I'm going to be useing this as a huge circular buffer that will just
On Tue, Jun 19, 2007 at 12:59:27PM -0700, Siddha, Suresh B wrote:
> hmm.. Please try this instead. This is intended only for debug. Based on your
> test results, we can comeup with a more decent fix.
This fixes the problem! Hurrah!
--D
signature.asc
Description: Digital signature
Hi Alexandre,
At some point in time, I wrote:
> Furthermore, Linus has repeatedly explained to you why he (and bunch
> of other _kernel_ hackers -- this is a thread on LKML, remember)
> thinks it's stupid for a software license to restrict hardware
> design choices.
On 6/19/07, Alexandre
When the old value and new one are the same the emulator skips the
write; this is undesiderable when the destination is a MMIO area and the
write shall be performed regardless of the previous value. This
optimization breaks e.g. a Linux guest APIC compiled without
X86_GOOD_APIC.
Remove the check
When writing to normal memory and the memory area is unchanged the write
can be safely skipped, avoiding the costly kvm_mmu_pte_write.
Signed-Off-By: Luca Tettamanti <[EMAIL PROTECTED]>
---
Tested with Fedora7, Solaris10 and WinXP on a 32 bit host with Intel
CPU.
drivers/kvm/kvm_main.c |
On Tue, Jun 19, 2007 at 02:03:07PM -0400, Chris Snook wrote:
> I pointed out NetApp's .snapshot directories because that's a method that
> uses legal path character, but doesn't break anything. With this method,
> userspace tools will have to be taught that : is suddenly a special
> character.
On Tue, Jun 19, Stephen Hemminger wrote:
> On Tue, 19 Jun 2007 21:02:53 +0200
> Olaf Hering <[EMAIL PROTECTED]> wrote:
>
> >
> > What happend to __ucmpdi2 from David Woodhouse?
> > google has a few hits about stuff like this on 32bit powerpc with gcc 4.1.2:
> >
> > ERROR: "__ucmpdi2"
On Tue, Jun 19, 2007 at 04:34:42PM -0400, John Stoffel wrote:
> > "Jack" == Jack Stone <[EMAIL PROTECTED]> writes:
>
> Jack> The whole idea of the file system is that it wouldn't return the
> Jack> file in the file listing. The user would have to know that the
> Jack> file system was
John Stoffel wrote:
>> "Jack" == Jack Stone <[EMAIL PROTECTED]> writes:
>
> Jack> The whole idea of the file system is that it wouldn't return the
> Jack> file in the file listing. The user would have to know that the
> Jack> file system was versioning to access the older versions as they
>
> "Jack" == Jack Stone <[EMAIL PROTECTED]> writes:
Jack> The whole idea of the file system is that it wouldn't return the
Jack> file in the file listing. The user would have to know that the
Jack> file system was versioning to access the older versions as they
Jack> would explicitly have to
> Right. All GPL can say is that you cannot impose further restrictions
> on how the user adapts the software, and since the user runs the
> software on that computer, that means you must not restrict the user's
> ability to upgrade or otherwise replace that software there, when you
> gave the
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is
Chris Snook wrote:
> Okay, so now you have to modify ls, cp, tar, and thousands of other
> applications to be aware of the versioning, otherwise you can't use it.
>
> Please don't get hung up on the interface. This is a really cool
> feature that will require some serious engineering work to
Not converted to the 2.6 kconfig system and no code in the tree.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
--- linux-2.6.22-rc4-mm2/drivers/scsi/Kconfig.old 2007-06-18
15:22:55.0 +0200
+++ linux-2.6.22-rc4-mm2/drivers/scsi/Kconfig 2007-06-18 15:23:04.0
+0200
@@
This patch removes the few leftovers of the MOMENCO_JAGUAR_ATX removal.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/Kconfig|2 +-
include/asm-mips/war.h |7 +++
2 files changed, 4 insertions(+), 5 deletions(-)
--- linux-2.6.22-rc4-mm2/drivers/net/Kconfig.old
This patch contains the scheduled removal of options depending
on OSS_OBSOLETE.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
sound/oss/Kconfig | 77 --
1 file changed, 77 deletions(-)
--- linux-2.6.22-rc4-mm2/sound/oss/Kconfig.old
On Mon, 2007-06-18 at 13:22 -0700, Christoph Lameter wrote:
> I think we are getting into more and more of a mess with the existing
> memory policies. The refcount issue with shmem is just one bad symptom of
> it. Memory policies were intended to be process based and
> taking them out of that
Il Mon, Jun 18, 2007 at 02:32:39PM +0300, Avi Kivity ha scritto:
> >Unfortunately, this kills Windows XP (first run with a guest crash,
> >second with a host oops), so I reverted it. I'd guess some operation
> >which doesn't need writeback ends up in the modified code.
> >Previously, the
On a faulty preempt disable bug we print out a warning but then we go
and call preempt_enable_no_resched, which also can print out a warning.
This is redundant.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
Index: linux-2.6.21-rt9/lib/smp_processor_id.c
Le mardi 19 juin 2007 à 21:56 +0200, Diego Calleja a écrit :
> Please, stop pretending you are hardware manufacturers. You are not.
Please, stop pretending the end user has no say in the GPL. The GPL (v2
or v3) is written with the end user not the hardware manufacturer in
mind.
Also I can tell
The show all regs sysrq uses the nmi function to do it. But this
function expects preemption to be off, or funny things happen.
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
Index: linux-2.6.21-rt9/drivers/char/sysrq.c
===
---
fb_find_logo() refences a few structs marked as __initdata. The structs
itself have a member ->data which is marked as __initdata as well.
scripts/pnmtologo.c write_footer() and write_header() create those
structs.
What is the correct fix, and why does it work at all?
-
To unsubscribe from this
Chris Snook wrote:
> Jack Stone wrote:
>> H. Peter Anvin wrote:
>>> Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is
Jack Stone wrote:
Chris Snook wrote:
Jack Stone wrote:
The idea was that if you did an ls you would get the latest version of
the file without the :revision_num. The only visible version would be
the latest version, i.e. the current system would not change. The idea
was that it would only show
On Tue, 19 Jun 2007 15:50:03 -0400
Jeff Dike <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 19, 2007 at 11:54:22AM -0700, Andrew Morton wrote:
> > On Tue, 19 Jun 2007 14:42:45 -0400
> > Jeff Dike <[EMAIL PROTECTED]> wrote:
> >
> > > Add a machanism to see how much of a kernel stack is used. This
> >
Currently NMI uses spinlocks to serialize the prints. We need these to
be raw spinlocks for PREEMPT_RT
Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
Index: linux-2.6.21-rt9/arch/x86_64/kernel/nmi.c
===
---
On Mon, Jun 18, 2007 at 02:56:10PM -0700, [EMAIL PROTECTED] wrote:
> yes, I'm useing promise drive shelves, I have them configured to export
> the 15 drives as 15 LUNs on a single ID.
>
> I'm going to be useing this as a huge circular buffer that will just be
> overwritten eventually 99% of the
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly a
special character.
Not to
101 - 200 of 1071 matches
Mail list logo
