Re: [RFC] Documentation/CodingStyle: Add rules for goto labels

WANG Cong wrote: > I just wonder, if a goto label is nested in a while/for/if/switch block, > aligning it in > the first column maybe a bit ugly. (I know mostly it is not in any > while/for/if/switch block.) > In general goto labels are not scoped, so there's no point in pretending they are.

Re: b44: regression in 2.6.22 (resend)

On Sun, 2007-06-03 at 18:26 +0200, Maximilian Engelhardt wrote: > > Is there any other strange behavior of the high res enabled kernel than > > the b44 problem ? > > I didn't notice anything in the past (as I wrote). But today I did some tests > for an updated version of the p54 mac80211 wlan dri

Re: [patch 1/2] ufd v1 - unsequential O(1) fdmap core

On Sun, 3 Jun 2007 15:51:13 -0700 (PDT) Davide Libenzi <[EMAIL PROTECTED]> wrote: > A bitmap allocator made sense because it has the property of making > allocations compact. Once that requirement is relaxed, it does not make > any sense to use it (and you have still to modify it in any case).

Re: BUG: sleeping function called from invalid context at kernel/fork.c:385

I see many many section mismatches when compiling with gcc 4.1 and binutils 2.17.50.20070426 They appear to be from .sdata to .init.data. This is with basic zx1_defconfig with a few mods. The reason appears to be compiler weirdness.. WARNING: init/built-in.o(.sdata+0x30): Section mismatch: r

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linus Torvalds wrote: > I actually think that a new system call is _hugely_ messy. It means that > anybody who wants to use a new feature needs to have a new glibc. Strange definition of "messy". Have you looked at the proposed dup2 extension? Magi

Re: A kexec approach to hibernation

Hi. I can see that the idea of writing a kernel image from using another kernel sounds nice and clean initially, but the more we get into the details (yes, I am listening, even though I said nothing before now), the more it's sounding like the cure is worse than the disease. To get rid of process

[PATCH ext3/ext4] orphan list check on destroy_inode

Customers claims to ext3-related errors, investigation showed that ext3 orphan list has been corrupted and have the reference to non-ext3 inode. The following debug helps to understand the reasons of this issue. Signed-off-by: Vasily Averin <[EMAIL PROTECTED]> diff --git a/fs/ext3/super.c b/fs

[RFC PATCH ext3/ext4] orphan list corruption due bad inode

After ext3 orphan list check has been added into ext3_destroy_inode() (please see my previous patch) the following situation has been detected: EXT3-fs warning (device sda6): ext3_unlink: Deleting nonexistent file (37901290), 0 Inode 0101a15b7840: orphan list check failed! 0773 6f665f0

[git pull] Input updates for 2.6.22-rc3

Hi Linus, Please consider pulling from: git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus or master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus to receive updates for input subsystem. Changelog: -- Dmitry Torokhov (3): Input

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

On Sun, 3 Jun 2007, Davide Libenzi wrote: > > Agreed, a new syscall looks less messy. I'll make sys_dup2() to allow > installing in the non-sequential area, only if there's an fd already > allocated. F_DUPFD will remain unchanged (that is, not allow > non-sequential fds allocations). I actua

Re: [RFC] Documentation/CodingStyle: Add rules for goto labels

On Sun, Jun 03, 2007 at 11:35:43AM -0400, Jeff Garzik wrote: >Randy Dunlap wrote: >>On Sun, 3 Jun 2007 15:29:39 +0100 Al Viro wrote: >> >>>On Sun, Jun 03, 2007 at 10:24:50PM +0800, WANG Cong wrote: >>> +Do care when you use Lindent to indent your code, since it may use spaces +instea

Kernel inclusion policy, meta desicion making structure?

Good day/evening to all. I was wondering if a meta version of the decision making process that would be employed to determine if a new contribution does or does not go into the main stream Linux kernel. The following abstract demonstrates my question if it does not make sense: "There are many fi

Re: A kexec approach to hibernation

On Fri, Jun 01, 2007 at 07:54:30PM -0400, Jeremy Maitin-Shepard wrote: > "Rafael J. Wysocki" <[EMAIL PROTECTED]> writes: > > > On Saturday, 2 June 2007 00:25, Jeremy Maitin-Shepard wrote: > > [snip] > > >> Just before jumping into the new kernel, with interrupts disabled, the > >> old kernel cou

RE: slow open() calls and o_nonblock

David Schwartz writes: [Aaron Wiebe] open("/somefile", O_WRONLY|O_NONBLOCK|O_CREAT, 0644) = 1621 <0.415147> How could they make any difference? I can't think of any conceivable way they could. Now, I'm a userspace guy so I can be pretty dense, but shouldn't a call with a nonblocking flag r

Re: [PATCH] reduce AER init error information

On Fri, 2007-06-01 at 05:04 -0700, Greg KH wrote: > On Tue, May 29, 2007 at 02:06:52PM -0700, Linus Torvalds wrote: > > > > > > On Tue, 29 May 2007, Greg KH wrote: > > > > > > Care to forward the above patch to the [EMAIL PROTECTED] address after > > > it goes into Linus's tree? > > > > .. talk

Re: Kconfig variable "COBALT" is not defined anywhere

That sounds correct. On 6/3/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: On Sun, 3 Jun 2007, Tim Hockin wrote: > I think the nvram is the only place left that uses CONFIG_COBALT sure, but once you remove this snippet near the top of drivers/char/nvram.c: ... # if defined(CONFIG_COBALT) #

Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip

On Monday 04 June 2007, Samuel Ortiz wrote: > Hi Andrey, > > On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote: > > Adding "nopnp" parameters finds device just fine so it is apparently > > result of this commit: > > > > commit d0d4f69bb65a8c1c1430c577a583632709b874c6 > > Author: Bjor

[PATCH -mm] Unionfs: Fix lock leak in unionfs_ioctl

(This patch is already in the Unionfs git tree. This is just a heads up.) Signed-off-by: Josef 'Jeff' Sipek <[EMAIL PROTECTED]> --- fs/unionfs/commonfops.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/unionfs/commonfops.c b/fs/unionfs/commonfops.c index 83001aa..10

Re: [PATCH] libata: CONFIG_PM=n compile fix

Hi. On Sun, 2007-06-03 at 17:58 -0500, Olof Johansson wrote: > CONFIG_PM=n compile fix. > > Signed-off-by: Olof Johansson <[EMAIL PROTECTED]> > > --- > > Hi, > > On Sat, May 26, 2007 at 11:09:54PM -0400, Jeff Garzik wrote: > > > This is checked into the 'mv-ahci-pata' branch of > > git://git.

Re: Patch related with Fork Bombing Atack

On Sunday 03 June 2007 19:01:21 Nix wrote: > On 1 Jun 2007, Jens Axboe told this: > > I think Anand is assuming that because syslog may coalesce identical > > messages into "repeated foo times" in the messages file, that it's not a > > dos. That is of course wrong. > > Not all syslog daemons do tha

Re: slow open() calls and o_nonblock

In article <[EMAIL PROTECTED]> you wrote: > In short, I'm distributing logs in realtime for about 600,000 > websites. The sources of the logs (http, ftp, realmedia, etc) are > flexible, however the base framework was build around a large cluster > of webservers. The output can be to several hundr

Re: slow open() calls and o_nonblock

On Sunday June 3, [EMAIL PROTECTED] wrote: > > You can certainly open the file, but not block on the call to do it. > What confuses me is why the kernel would "block" for 415ms on an open > call. Thats an eternity to suspend a process that has to distribute > data such as this. Have you tried th

Re: slow open() calls and o_nonblock

In article <[EMAIL PROTECTED]> you wrote: > (ps. having come from the socket side of the fence, its incredibly > frustrating to be unable to poll() or epoll regular file FDs -- > Especially knowing that the kernel is translating them into a TCP > socket to do NFS anyway. Please add regular files

Re: [RFC PATCH]Multi-threaded Initcall with dependence support

On Friday 01 June 2007 04:26, Dave Jones wrote: > On Tue, May 29, 2007 at 09:47:53AM +0800, Yang Sheng wrote: > > On Tuesday 29 May 2007 06:52, Randy Dunlap wrote: > > > On Mon, 28 May 2007 15:03:10 +0800 Yang Sheng wrote: > > > > Why we need this: > > > > > > > > It can speed up the calling o

Re: slow open() calls and o_nonblock

Hi John, thanks for responding. I'm using kernel 2.6.20 on a home-grown distro. I've responded to a few specific points inline - but as a whole, Davide directed me to work that is being done specifically to address these issues in the kernel, as well as a userspace implementation that would allo

Re: slow open() calls and o_nonblock

On Sun, Jun 03, 2007 at 05:27:06PM -0700, David Schwartz wrote: > > > Now, Netapp speed aside, O_NONBLOCK and O_DIRECT seem to make zero > > difference to my open times. Example: > > > > open("/somefile", O_WRONLY|O_NONBLOCK|O_CREAT, 0644) = 1621 <0.415147> > The 'open' function must, at minimu

Re: [RFC 0/4] CONFIG_STABLE to switch off development checks

On Sat, 2007-06-02 at 09:28 -0700, Jeremy Fitzhardinge wrote: > Dave Kleikamp wrote: > > I'm on Christoph's side here. I don't think it makes sense for any code > > to ask to allocate zero bytes of memory and expect valid memory to be > > returned. > > > > Yes, everyone agrees on that. If you

Re: [3/3] 2.6.22-rc3: known regressions with patches v2

At Fri, 01 Jun 2007 14:22:03 +0200, Michal Piotrowski wrote: > Subject: signal: multithread program returns with wrong errno on > receiving SIGSTOP > References : http://lkml.org/lkml/2007/5/27/189 > Submitter : Satoru Takeuchi <[EMAIL PROTECTED]> > Handled-By : Oleg Nesterov <[EMAIL PROTECTE

Re: [PATCH] sendfile removal

Hi Jens, This is another try, still not in a comfortable state though. //Busy waiting is possible for interleaved reads. Fengguang --- In non-block splicing read, return EAGAIN once for possible I/O waits. It avoids busy waiting by checking (ra.prev_index != index) in __generic_file_splice_read

Re: libata & no PCI: dma_[un]map_single undefined

From: Meelis Roos <[EMAIL PROTECTED]> Date: Sun, 3 Jun 2007 23:23:33 +0300 (EEST) > I accidentally enabled libata config options on my Sun Ultra 1 (sparc64, > UP, no PCI, only SBUS): > > MODPOST 440 modules > ERROR: "dma_unmap_sg" [drivers/ata/libata.ko] undefined! > ERROR: "dma_map_sg" [drive

3Com 3c905: Resetting the Tx ring pointer.

Hi, Old kernel 2.6.20.1, is OK. After update to kernel 2.6.21.3, ethernet controller freeze after ~6hours-12hours. Any opinion? Hundreds of this message is on syslog: Jun 3 18:36:27 zeus kernel: NETDEV WATCHDOG: eth0: transmit timed out Jun 3 18:36:27 zeus kernel: eth0: transmit timed out, t

RE: slow open() calls and o_nonblock

> Now, Netapp speed aside, O_NONBLOCK and O_DIRECT seem to make zero > difference to my open times. Example: > > open("/somefile", O_WRONLY|O_NONBLOCK|O_CREAT, 0644) = 1621 <0.415147> How could they make any difference? I can't think of any conceivable way they could. > Now, I'm a userspace guy

[PATCH] HFSPlus: change kmalloc/memset to kzalloc

From: Wyatt Banks <[EMAIL PROTECTED]> Removed kmalloc and memset in favor of kzalloc. Signed-off-by: Wyatt Banks <[EMAIL PROTECTED]> --- Patched against 2.6.21.3 To explain the HFSPLUS_SB() macro in the removed memset call: hfsplus_fs.h:#define HFSPLUS_SB(super) (*(struct hfsplus_sb_info

Re: slow open() calls and o_nonblock

> "Aaron" == Aaron Wiebe <[EMAIL PROTECTED]> writes: More details on which kernel you're using and which distro would be helpful. Also, more details on your App and reasons why you're writing bunches of small files would help as well. Aaron> Greetings all. I'm not on this list, so I apolog

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

On Sun, 3 Jun 2007, Ulrich Drepper wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Davide Libenzi wrote: > > Randomizing the base is not a problem. Should this be always, or flag > > driven? > > I would say all the time. I don't think it's a problem with > reproducibility in any r

[PATCH] [2.6.22] libata: fix probe time irq printouts

Most drivers don't seem to fill out the host->irq field, resulting in the wrong (no) irq being reported at probe time. For example, sil24 on my system: ata1: SATA max UDMA/100 cmd 0xd8009001f000 ctl 0x bmdma 0x irq 0 ata2: SATA max UDMA/100 cmd 0xd800900210

Re: Patch related with Fork Bombing Atack

On 1 Jun 2007, Jens Axboe told this: > I think Anand is assuming that because syslog may coalesce identical > messages into "repeated foo times" in the messages file, that it's not a > dos. That is of course wrong. Not all syslog daemons do that, anyway. (syslog-ng doesn't, for one.) -- `On a sc

Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip

Hi Andrey, On Sun, Jun 03, 2007 at 12:16:05PM +0400, Andrey Borzenkov wrote: > > Adding "nopnp" parameters finds device just fine so it is apparently result > of > this commit: > > commit d0d4f69bb65a8c1c1430c577a583632709b874c6 > Author: Bjorn Helgaas <[EMAIL PROTECTED]> > Date: Tue May 8 0

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Davide Libenzi wrote: > Randomizing the base is not a problem. Should this be always, or flag > driven? I would say all the time. I don't think it's a problem with reproducibility in any reasonable code. - -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

On Sun, 3 Jun 2007, Ulrich Drepper wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Davide Libenzi wrote: > >> If randomizing each allocator is too expensive then randomize at the > >> very least the number of the first descriptor you give out. > > > > Can you tell me how this can be

Re: [RFC][PATCH -mm 1/2] PM: Introduce hibernation and suspend notifiers

On Mon 2007-06-04 00:38:53, Rafael J. Wysocki wrote: > On Sunday, 3 June 2007 18:41, Pavel Machek wrote: > > Hi! > > > > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > > > Make it possible to register hibernation and suspend notifiers, so that > > > subsystems can perform hibernation-relat

[PATCH] libata: CONFIG_PM=n compile fix

CONFIG_PM=n compile fix. Signed-off-by: Olof Johansson <[EMAIL PROTECTED]> --- Hi, On Sat, May 26, 2007 at 11:09:54PM -0400, Jeff Garzik wrote: > This is checked into the 'mv-ahci-pata' branch of > git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git Didn't build for me withou

Re: [patch 1/2] ufd v1 - unsequential O(1) fdmap core

On Sun, 3 Jun 2007, Eric Dumazet wrote: > Davide Libenzi a ?crit : > > Core code for the unsequential fdmap implementation. Random allocation, > > exact allocation, de-allocation and lookup are all O(1) operations. > > The only operation that is O(N) is the strict from-N-up kind of allocation, > >

Re: [PATCH 05/19] kbuild: document cc-fullversion

On Sun, 3 Jun 2007 22:46:03 +0200 Sam Ravnborg wrote: > Subject: [PATCH 05/19] kbuild: document cc-fullversion > From: Sam Ravnborg <[EMAIL PROTECTED]> > Date: Mon, 28 May 2007 22:26:55 +0200 > > Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> > --- > Documentation/kbuild/makefiles.txt | 14 ++

Re: [RFC][PATCH -mm 1/2] PM: Introduce hibernation and suspend notifiers

On Sunday, 3 June 2007 18:41, Pavel Machek wrote: > Hi! > > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > Make it possible to register hibernation and suspend notifiers, so that > > subsystems can perform hibernation-related or suspend-related operations > > that > > should not be carrie

Re: [PATCH] ACPI Debug - for test, devel and possibly even for production kernels

Hello Thomas, I'm delighted that you feel that the ACPI debug code is worthy of being enabled by default in SuSE Linux. While that certainly wasn't the intent of the code, I'm open to your suggestions should you find any issues with it where it doesn't suite your needs. However, I have no plans

Re: Define CONFIG_BOUNCE to avoid useless inclusion of bounce buffer logic.

On Wed, May 23, 2007 at 09:03:02PM -0700, Christoph Lameter wrote: > On Thu, 24 May 2007, Paul Mackerras wrote: > > Also there is the problem that some drivers use ZONE_DMA allocations > > because their device can only generate addresses below some limit, but > > on a platform with an IOMMU there i

Re: [Patch 14/18] fs/logfs/segment.c

On Sunday 03 June 2007, Jörn Engel wrote: > +static DEFINE_MUTEX(compr_mutex); > + It seems you define a static compre_mutex in both segment.c and in compr.c, and always lock them both at the same time. Is that a correct observation? Is it intentional, or an oversight on your side? Arnd <

Re: LogFS take four

On Sunday 03 June 2007, Jörn Engel wrote: > Unchanged: > o error handling > ... > Won't happen (unless I get convinced to do otherwise): > o Change LOGFS_BUG() and LOGFS_BUG_ON() to inline functions > These are macros for very much the same reasons BUG() and BUG_ON() are. I wonder how many of

[PATCH 1/1] Char: stallion, don't fail with less than max panels

Ingo Korb wrote: > Stallion Multiport Serial Driver: version 5.6.0 > stallion :00:0b.0: please, report this to LKML: 100b/d001/ff > ACPI: PCI Interrupt :00:0b.0[A] -> GSI 19 (level, low) -> IRQ 17 > stallion: probe of :00:0b.0 failed with error -16 > === Cut === > > The card is a EC

Re: [Patch 06/18] fs/logfs/compr.c

On Sunday 03 June 2007, Jörn Engel wrote: > +#define COMPR_LEVEL 3 > + > +static DEFINE_MUTEX(compr_mutex); > +static struct z_stream_s stream; Is there a particular reason to choose '3' as the only compression level? Should this perhaps be a per-superblock option instead? Also, I thought I saw d

[PATCH] COBALT: Remove all traces of COBALT from nvram.c

Drop all references to the COBALT arch from drivers/char/nvram.c. Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> --- diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c index 204deaa..98dec38 100644 --- a/drivers/char/nvram.c +++ b/drivers/char/nvram.c @@ -42,19 +42,12 @@ #define PC

Re: Kconfig variable "COBALT" is not defined anywhere

On Sun, 3 Jun 2007, Tim Hockin wrote: > I think the nvram is the only place left that uses CONFIG_COBALT sure, but once you remove this snippet near the top of drivers/char/nvram.c: ... # if defined(CONFIG_COBALT) #include #define MACH COBALT # else #define MACH PC # endif ... t

Re: [Patch 04/18] include/linux/logfs.h

On Sunday 03 June 2007, Jörn Engel wrote: > +struct logfs_je_spillout { > +   __be64  so_segment[0]; > +}__packed; All the on-disk data structures you define in this file have naturally aligned members, so the __packed attribute is not needed. However, I think it causes gcc to generate larger

Re: Kconfig variable "COBALT" is not defined anywhere

I think the nvram is the only place left that uses CONFIG_COBALT On 6/3/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote: On Sun, 3 Jun 2007, Tim Hockin wrote: > There were other patches which added more COBALT support, but they > were dropped or lost or whatever. > > I would not balk at having t

[BUG] Oops with KVM-27

Hello, my kernel just exploded :) The host is running 2.6-git-current, with KVM modules from KVM-27 package. kernel is 32bit, SMP, with PREEMPT enabled, no HIGHMEM (but I'm using CONFIG_VMSPLIT_3G_OPT=y). The CPU is a Core2 (hence I'm using kvm-intel). Guest was a Fedora7 setup DVD, which died som

Re: [2.6.22-rc3][ACPI?] Resume from s2r doesn't work.

"Rafael J. Wysocki" <[EMAIL PROTECTED]> writes: > Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the > place where it really fails. First I augmented my minimal config kernel with some TRACE_RESUME()s: --- a/kernel/power/main.c 2007-05-27 23:48:05.0 +0200 +++

Re: [patch 1/2] ufd v1 - unsequential O(1) fdmap core

Davide Libenzi a écrit : Core code for the unsequential fdmap implementation. Random allocation, exact allocation, de-allocation and lookup are all O(1) operations. The only operation that is O(N) is the strict from-N-up kind of allocation, but that only used by F_DUPFD and it's definitely not fr

Re: Kconfig variable "COBALT" is not defined anywhere

On Sun, 3 Jun 2007, Tim Hockin wrote: > There were other patches which added more COBALT support, but they > were dropped or lost or whatever. > > I would not balk at having that code yanked. I never got around to > doing proper Cobalt support for modern kernels. :( > > On 6/3/07, Roland Dreier <

Re: stallion driver dmesg notice

Ingo Korb napsal(a): > Hi! > > The stallion driver in 2.6.21.3 put this little notice in my dmesg: > > === Cut === > Stallion Multiport Serial Driver: version 5.6.0 > stallion :00:0b.0: please, report this to LKML: 100b/d001/ff > ACPI: PCI Interrupt :00:0b.0[A] -> GSI 19 (level, low)

Re: [kbuild-devel] kbuild update

On Sun, Jun 03, 2007 at 05:04:39PM -0400, Chris Smith wrote: > >What's next? > >... > >-> A few cygwin specific changes may hit kbuild - to allow the kernel to > >be built > > using cygwin on a windoze box. > > This seems vaguely immoral. ;) Especially embedded people like to build on Windoze b

Re: Kconfig variable "COBALT" is not defined anywhere

There were other patches which added more COBALT support, but they were dropped or lost or whatever. I would not balk at having that code yanked. I never got around to doing proper Cobalt support for modern kernels. :( On 6/3/07, Roland Dreier <[EMAIL PROTECTED]> wrote: > > > there is no Kc

Re: [kbuild-devel] kbuild update

What's next? ... -> A few cygwin specific changes may hit kbuild - to allow the kernel to be built using cygwin on a windoze box. This seems vaguely immoral. ;) Thanks, Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTE

Re: Device hang when offlining a CPU due to IRQ misrouting

> > This is just getting confusing. > > Emmanuel Fust. Please play with /proc/irq/*/smp_affinity by and and > confirm that you can move your irqs. This will confirm it is the decision > part. > Ok, as planned, you're right ;-) , playing with /proc/irq/*/smp_affinity let me move irqs. Emmanuel

[-mm patch] make xpad_play_effect() static

On Wed, May 30, 2007 at 11:58:23PM -0700, Andrew Morton wrote: >... > Changes since 2.6.22-rc2-mm1: >... > git-input.patch >... > git trees >... This patch makes the needlessly global xpad_play_effect() static. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- --- linux-2.6.22-rc3-mm1/drivers

[-mm patch] fix the tea5761 tuner support

On Wed, May 30, 2007 at 11:58:23PM -0700, Andrew Morton wrote: >... > Changes since 2.6.22-rc2-mm1: >... > git-dvb.patch >... > git trees >... Due to a typo the tea5761 tuner support was dead code. This patch also fixes a bug in the no longer dead code: A void function can't return anything. S

[-mm patch] make drivers/firmware/dmi-id.c:dmi_id_init() static

This patch makes the needlessly global dmi_id_init() static. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- --- linux-2.6.22-rc3-mm1/drivers/firmware/dmi-id.c.old 2007-06-03 22:17:10.0 +0200 +++ linux-2.6.22-rc3-mm1/drivers/firmware/dmi-id.c 2007-06-03 22:17:24.0 +0200

[-mm patch] drivers/i2c/chips/ds1682.c: make code static

This patch makes some needlessly global code static. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- drivers/i2c/chips/ds1682.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) --- linux-2.6.22-rc3-mm1/drivers/i2c/chips/ds1682.c.old 2007-06-03 22:18:53.0 +0200 +

Re: kbuild update

Hmm, the patch serie should have been chained. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[2.6 patch] remove dead MTD_PMC551_APERTURE_SIZE option

The CONFIG_MTD_PMC551_APERTURE_SIZE option seems to never have existed, so there's no reason for carrying an #ifdef for it. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- --- linux-2.6.22-rc3-mm1/drivers/mtd/devices/pmc551.c.old 2007-06-03 19:16:00.0 +0200 +++ linux-2.6.22-rc3

[PATCH 19/19] kbuild: whitelist references from variables named _timer to .init.text

Subject: [PATCH 19/19] kbuild: whitelist references from variables named _timer to .init.text From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sun, 3 Jun 2007 22:19:24 +0200 arm uses a lot of ops structures named *_timer that has legitimite references to .init.text. So let's add this variable to the

[PATCH 17/19] kbuild: refactor code in modpost

Subject: [PATCH 17/19] kbuild: refactor code in modpost From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sun, 3 Jun 2007 00:41:22 +0200 Move more checks from whitelist to the section check functions Renumber the patterns. No functional changes. Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- scri

[PATCH 18/19] kbuild: remove hardcoded _logo names from modpost

Subject: [PATCH 18/19] kbuild: remove hardcoded _logo names from modpost From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sun, 3 Jun 2007 00:47:53 +0200 Replaced this with a __init_refok marker in front of fb_find_logo(). I think that the __initdata marker for the logo's are wrong but I have not just

[PATCH 14/19] kbuild: refactor code in modpost to improve maintainability

Subject: [PATCH 14/19] kbuild: refactor code in modpost to improve maintainability From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sat, 2 Jun 2007 21:18:51 +0200 There were a great deal of overlap between the two functions that check which sections may reference .init.text and .exit.text. Factor out

[PATCH 15/19] kbuild: warn about references from .init.text to .exit.text

Subject: [PATCH 15/19] kbuild: warn about references from .init.text to .exit.text From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sat, 2 Jun 2007 21:29:20 +0200 The .exit.text section may be discarded either at build or at runtime. So let modpost warn if this situation is detected. Signed-off-by:

[PATCH 16/19] kbuild: remove hardcoded apic_es7000 from modpost

Subject: [PATCH 16/19] kbuild: remove hardcoded apic_es7000 from modpost From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Sun, 3 Jun 2007 00:05:10 +0200 Replace the hardcoded variable name apic_es7000 in modpost with a __initdata_refok marker. Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- arch

[PATCH 13/19] kbuild: ignore section mismatch warnings originating from .note section

Subject: [PATCH 13/19] kbuild: ignore section mismatch warnings originating from .note section From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Tue, 29 May 2007 23:09:35 +0200 .note* sections are ELF notes, which are typically used by external tools to examine the kernel image. Since this is removed

stallion driver dmesg notice

Hi! The stallion driver in 2.6.21.3 put this little notice in my dmesg: === Cut === Stallion Multiport Serial Driver: version 5.6.0 stallion :00:0b.0: please, report this to LKML: 100b/d001/ff ACPI: PCI Interrupt :00:0b.0[A] -> GSI 19 (level, low) -> IRQ 17 stallion: probe of :00:

[PATCH 11/19] kbuild: add support for squashing uid/gid in gen_initramfs_list.sh

Subject: [PATCH 11/19] kbuild: add support for squashing uid/gid in gen_initramfs_list.sh From: Mike Frysinger <[EMAIL PROTECTED]> Date: Thu, 10 May 2007 22:44:28 -0700 Sometimes it is useful to squash all uid's/gid's to 0:0 regardless of current owner. For example, in build systems that get run

[PATCH 12/19] kbuild: The .paravirtprobe section is obsolete, so modpost doesn't need to handle it

Subject: [PATCH 12/19] kbuild: The .paravirtprobe section is obsolete, so modpost doesn't need to handle it From: Jeremy Fitzhardinge <[EMAIL PROTECTED]> Date: Tue, 29 May 2007 13:33:01 -0700 The .paravirtprobe section is obsolete, so modpost doesn't need to handle it. Signed-off-by: Jeremy Fitz

[PATCH 10/19] kbuild: add support for reading stdin with gen_init_cpio

Subject: [PATCH 10/19] kbuild: add support for reading stdin with gen_init_cpio From: Mike Frysinger <[EMAIL PROTECTED]> Date: Thu, 10 May 2007 22:44:28 -0700 Treat an argument of "-" as meaning "read stdin for cpio files" so gen_init_cpio can be piped into. Signed-off-by: Mike Frysinger <[EMAIL

[PATCH 10/19] kbuild: add support for reading stdin with gen_init_cpio

Subject: [PATCH 10/19] kbuild: add support for reading stdin with gen_init_cpio From: Mike Frysinger <[EMAIL PROTECTED]> Date: Thu, 10 May 2007 22:44:28 -0700 Treat an argument of "-" as meaning "read stdin for cpio files" so gen_init_cpio can be piped into. Signed-off-by: Mike Frysinger <[EMAIL

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Davide Libenzi wrote: >> If randomizing each allocator is too expensive then randomize at the >> very least the number of the first descriptor you give out. > > Can you tell me how this can be a problem, and in which way making a > random thing would

[PATCH 09/19] kconfig: use POSIX equality test in check-lxdialog.sh

Subject: [PATCH 09/19] kconfig: use POSIX equality test in check-lxdialog.sh From: Mike Frysinger <[EMAIL PROTECTED]> Date: Wed, 23 May 2007 21:37:45 -0400 The "==" operator is not in POSIX, so use -eq instead. Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]> Signed-off-by: Sam Ravnborg <[EMAIL

[PATCH 07/19] kbuild: avoid environment to set variables used by kbuild

Subject: [PATCH 07/19] kbuild: avoid environment to set variables used by kbuild From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Mon, 28 May 2007 22:47:48 +0200 A few of the variables used by kbuild has fixed naming. Make sure we do not pick up random values from the environment. Signed-off-by: Sam

[PATCH 08/19] scripts: Make cleanfile/cleanpatch warn about long lines

Subject: [PATCH 08/19] scripts: Make cleanfile/cleanpatch warn about long lines From: H. Peter Anvin <[EMAIL PROTECTED]> Date: Fri, 25 May 2007 17:58:26 -0700 Make the "cleanfile" and "cleanpatch" script warn about long lines, by default lines whose visual width exceeds 79 characters. Per suggest

Re: Kconfig variable "COBALT" is not defined anywhere

> > > there is no Kconfig file which defines the selectable option > > > "COBALT", which means that this snippet from drivers/char/nvram.c: > > > > > > # if defined(CONFIG_COBALT) > > > #include > > > #define MACH COBALT > > > # else > > > #define MACH PC > > > # endif >

[PATCH 06/19] kbuild: suppress modpost warnings for references from the .toc section as used by powerpc

Subject: [PATCH 06/19] kbuild: suppress modpost warnings for references from the .toc section as used by powerpc From: Stephen Rothwell <[EMAIL PROTECTED]> Date: Thu, 24 May 2007 14:16:13 +1000 We should do better here by effetively "dereferencing" references to the .toc (or the .got2) section, b

[PATCH 03/19] kbuild: New 'cc-fullversion' macro

Subject: [PATCH 03/19] kbuild: New 'cc-fullversion' macro From: Segher Boessenkool <[EMAIL PROTECTED]> Date: Sat, 19 May 2007 18:49:07 +0200 Prints a six-digit string including the GCC patchlevel. Also fix the 'usage' comment for cc-version. Signed-off-by: Segher Boessenkool <[EMAIL PROTECTED]>

[PATCH 04/19] powerpc: Refuse to build 64-bit with GCC-4.2.0 and CONFIG_MODULES

Subject: [PATCH 04/19] powerpc: Refuse to build 64-bit with GCC-4.2.0 and CONFIG_MODULES From: Segher Boessenkool <[EMAIL PROTECTED]> Date: Sat, 19 May 2007 18:49:08 +0200 ...since this won't work (compiler bug, see ). Signed-off-by: Segher Boessenkool <[EMAIL PROTECT

[PATCH 05/19] kbuild: document cc-fullversion

Subject: [PATCH 05/19] kbuild: document cc-fullversion From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Mon, 28 May 2007 22:26:55 +0200 Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- Documentation/kbuild/makefiles.txt | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff

[PATCH 02/19] kbuild: make better section mismatch reports on i386, arm and mips

Subject: [PATCH 02/19] kbuild: make better section mismatch reports on i386, arm and mips From: Atsushi Nemoto <[EMAIL PROTECTED]> Date: Tue, 22 May 2007 18:27:39 +0900 On i386, ARM and MIPS, warn_sec_mismatch() sometimes fails to show usefull symbol name. This is because empty 'refsym' due to 0

[PATCH 01/19] kbuild: asm-offsets.h is now cleaned with O=.. builds

Subject: [PATCH 01/19] kbuild: asm-offsets.h is now cleaned with O=.. builds From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Mon, 28 May 2007 22:14:37 +0200 Reported by: "Robert P. J. Day" <[EMAIL PROTECTED]> Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> Cc: "Robert P. J. Day" <[EMAIL PROTECTED]>

kbuild update

Short intro to content of kbuild.git at the moment. See http://git.kernel.org/?p=linux/kernel/git/sam/kbuild.git;a=summary Everything are targeted for next merge window. section mismatch kbuild: make better section mismatch reports on i386, arm and mips kbuild: The .paravirtprobe sect

Re: Kconfig variable "COBALT" is not defined anywhere

On Sun, 3 Jun 2007, Randy Dunlap wrote: > On Sun, 3 Jun 2007 13:17:48 -0400 (EDT) Robert P. J. Day wrote: > > > > > (no one's listed as the official cobalt maintainer so i thought i'd > > just throw this out there.) > > > > there is no Kconfig file which defines the selectable option > > "COBA

Re: How to access correctly serial port inside module?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tilman Schmidt schrieb: Am 17.05.2007 08:15 schrieb huang ying: I think the "serio" (through drivers/input/serio/serport.c) may be a choice too, like that in linux/drivers/input/mouse/sermouse.c, which is an example to program serial port in kernel

Re: Kconfig variable "COBALT" is not defined anywhere

On Sun, 3 Jun 2007 13:17:48 -0400 (EDT) Robert P. J. Day wrote: > > (no one's listed as the official cobalt maintainer so i thought i'd > just throw this out there.) > > there is no Kconfig file which defines the selectable option > "COBALT", which means that this snippet from drivers/char/n

libata & no PCI: dma_[un]map_single undefined

I accidentally enabled libata config options on my Sun Ultra 1 (sparc64, UP, no PCI, only SBUS): MODPOST 440 modules ERROR: "dma_unmap_sg" [drivers/ata/libata.ko] undefined! ERROR: "dma_map_sg" [drivers/ata/libata.ko] undefined! ERROR: "dma_unmap_single" [drivers/ata/libata.ko] undefined! ERROR

Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap

On Sun, 3 Jun 2007, Ulrich Drepper wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Davide Libenzi wrote: > >> I agree with Ingo, no need for a second magic value. Use the same value > >> as FD_UNSEQ_ALLOC which will just mean this exact value should never be > >> used as a file des

[PATCH 3/2] serverworks: always tune CSB6

[ yeah, this is a follow-up to yesterdays' patches thus #3/2 ] Switch the driver to always program DMA/PIO timings and set device transfer mode instead of trusting BIOS on CSB6 controllers (libata pata_serverworks.c driver is also doing things this way and there were no problems reported so far).

  1   2   3   >