From: Greg KH <gregkh@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
kay.sievers@vrfy.org, Michael_E_Brown@dell.com,
rdreier@cisco.com, htejun@gmail.com
Subject: Re: [GIT PATCH] driver core fixes against 2.6.25-rc2 git
Date: Fri, 22 Feb 2008 11:56:52 -0800 [thread overview]
Message-ID: <20080222195652.GA6395@suse.de> (raw)
In-Reply-To: <20080222075625.GA2660@uranus.ravnborg.org>
On Fri, Feb 22, 2008 at 08:56:25AM +0100, Sam Ravnborg wrote:
> Hi Greg.
>
> On Thu, Feb 21, 2008 at 03:46:49PM -0800, Greg KH wrote:
> > Here are a few driver core fixes against your current git tree that fix some
> > more problems that have cropped up:
> > - shutdown problem due to logic problem with cpufreq usage of
> > kobjects.
> > - build fix for powerpc due to previous kobject changes.
> > - runtime errors when CONFIG_SYSFS=n
> > - UIO code now works properly from my previous messups
> > - proper encoding of the ja_JP stable_kernel_rules.txt file
> > - updates to the stable_kernel_rules.txt file
> > - mark ide=reverse as obsolete in preparation of 2.6.26 (Bart
> > wanted this to go in through my tree as I have the .26 patches
> > pending.)
> > - other minor fixes.
>
>
> Do we have any outstanding issues with section mismatch warnings in PCI Core?
> I am as always optimistic and hope to get down to zero warnings soon.
I do not know, I saw your patches earlier and thought that they were
going in through another tree for some reason. If you still see any
remaining, please send me the needed patches again.
thanks,
greg k-h
next prev parent reply other threads:[~2008-02-22 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:46 [GIT PATCH] driver core fixes against 2.6.25-rc2 git Greg KH
2008-02-21 23:47 ` [PATCH 01/11] Fix broken utf-8 encodings in ja_JP translation of stable_kernel_rules.txt Greg Kroah-Hartman
2008-02-21 23:47 ` [PATCH 02/11] slabinfo: fall back from /sys/kernel/slab to /sys/slab Greg Kroah-Hartman
2008-02-21 23:47 ` [PATCH 03/11] cpufreq: fix kobject reference count handling Greg Kroah-Hartman
2008-02-21 23:53 ` Dave Jones
2008-02-21 23:48 ` [PATCH 04/11] driver-core: fix kernel-doc function parameters Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 05/11] Driver core: Fix error handling in bus_add_driver() Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 06/11] ide: mark "ide=reverse" option as obsolete Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 07/11] stable_kernel_rules: fix must already be in mainline Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 08/11] UIO: fix Greg's stupid changes Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 09/11] PM: Remove unbalanced mutex_unlock() from dpm_resume() Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 10/11] POWERPC: fix typo in pseries/power.c Greg Kroah-Hartman
2008-02-21 23:48 ` [PATCH 11/11] modules: do not try to add sysfs attributes if !CONFIG_SYSFS Greg Kroah-Hartman
2008-02-22 7:56 ` [GIT PATCH] driver core fixes against 2.6.25-rc2 git Sam Ravnborg
2008-02-22 19:56 ` Greg KH [this message]
2008-02-22 20:07 ` Sam Ravnborg
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=20080222195652.GA6395@suse.de \
--to=gregkh@suse.de \
--cc=Michael_E_Brown@dell.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=htejun@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sam@ravnborg.org \
--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