mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg KH <gregkh@suse.de>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz,
	pcihpd-discuss@lists.sourceforge.net
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Mon, 6 Mar 2006 23:47:05 +0100	[thread overview]
Message-ID: <20060306224705.GA29509@mars.ravnborg.org> (raw)
In-Reply-To: <20060306223545.GA20885@kroah.com>

On Mon, Mar 06, 2006 at 02:35:45PM -0800, Greg KH wrote:
> Here's a summary of the current state of the Linux PCI and PCI Hotplug
> subsystems as of 2.6.16-rc5
> 
> If the information in here is incorrect, or anyone knows of any
> outstanding issues not listed here, please let me know.

Not an direct outstanding issue, but more a TODO.
The section mismatch check that is now part of a regular kernel build
(in -mm) detected a number of cases with inconsistency in __devinit
versus __init usage. Some are still outstanding and needs to be fixed.

The natural next step is to extend the check to cover __devinit,
__devinitdata so we to some extent knows things are consistent should
someone decide to build a kernel without hotplug enabled.

The task is simple enough:
Add a new section for __devinit, __devinitdata
Add consistency check in modpost.

I took a short look at it, but done right stuff from vmlinux.lds ought
to be consolidated in asm-generaic/vmlinux.lds.h, but my head started
spinning when I went through the different $(ARCH)/kernel/vmlinux.lds
files.

2.6.18 material - we are not in a hurry.
Fixes for the warnings always generated are 2.6.17 material if people
start fixing them soon (when the check hits mainline I assume this will
happen).

> Was this summary useful for people?  Anything that I should add to it?

Useful - maybe. But indeed interesting reading (also the USB part).

	Sam

  reply	other threads:[~2006-03-06 22:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:35 Greg KH
2006-03-06 22:47 ` Sam Ravnborg [this message]
2006-03-06 23:00   ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50   ` Greg KH
2006-03-08 23:03     ` Linus Torvalds
2006-03-08 23:18       ` Greg KH
2006-03-08 23:30         ` Linus Torvalds
2006-03-09 18:40           ` Tomasz Torcz
2006-03-09 19:49             ` Linus Torvalds
2006-03-09 20:10               ` Ben Collins
2006-03-09 20:24                 ` Linus Torvalds
2006-03-15 16:03                   ` Ben Collins
2006-03-09 20:52                 ` Lee Revell
2006-03-09 21:06                   ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47                     ` Lee Revell
2006-03-09 21:07                   ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37               ` Arjan van de Ven
2006-03-09 20:46                 ` Dave Jones
2006-03-09 21:15                   ` Arjan van de Ven
2006-03-08 23:29       ` Andrew Morton
2006-03-08 23:45         ` Dave Hansen
2006-03-08 23:52           ` Andrew Morton
2006-03-09 10:24         ` Martin MOKREJŠ
2006-03-08 23:05     ` Adrian Bunk
2006-03-08 23:18       ` Lee Revell
2006-03-08 23:23         ` Greg KH
2006-03-08 23:34           ` Lee Revell
2006-03-08 23:40             ` Greg KH
2006-03-09  0:03               ` Lee Revell
2006-03-08 23:21       ` Greg KH
2006-03-09  4:01 ` Kenji Kaneshige
2006-03-09  5:34   ` Greg KH
2006-03-09  5:11 ` Lee Revell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060306224705.GA29509@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome