From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: left over things in linux-next after 2.6.28-c1
Date: Sat, 25 Oct 2008 14:20:37 -0700 [thread overview]
Message-ID: <20081025212037.GB32027@kroah.com> (raw)
In-Reply-To: <20081026005009.50dbbb33.sfr@canb.auug.org.au>
On Sun, Oct 26, 2008 at 12:50:09AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following is an approximate list of commits left in linux-next
> relative to 2.6.28-rc1. Some things here may have been included in
> Linus' tree in a slightly different form. The kvm tree is excluded from
> this list because the bits of it submitted to Linus are often different
> to what is in linux-next (my scipt says that it has ~1400 outstanding
> commits).
Nice report, thanks for doing this.
> driver-core.current
>
> Andi Kleen (1):
> sysfs: Fix return values for sysdev_store_{ulong,int}
>
> Greg Kroah-Hartman (1):
> Document kernel taint flags properly
>
> Qinghuang Feng (1):
> driver core: drivers/base/sys.c: update comments
Yes, all of these will be sent to Linus soon.
> usb
>
> Denis Joseph Barrow (2):
> HSO: fix hso_serial_close refcounting
> HSO: put linefeeds on printk's in hso.c
I'm holding on to these so they don't get lost, but Denis is reworking
them at the moment to make them fix the problems correctly.
> Greg Kroah-Hartman (2):
> USB: remove warn() macro from usb.h
> USB: remove info() macro from usb.h
I had hopes for these to be merged, but don't think they will be due to
some remaining usages in the media tree. I'll wait until 2.6.29 to push
them in.
> xfs
<snip>
wow, did XFS ever merge with Linus? That looks like a lot of
outstanding patches :(
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-25 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 13:50 linux-next: left over things in linux-next after 2.6.28-c1 Stephen Rothwell
2008-10-25 13:58 ` Al Viro
2008-10-25 14:37 ` Sam Ravnborg
2008-10-25 21:16 ` Greg KH
2008-10-25 21:52 ` Sam Ravnborg
2008-10-25 22:10 ` Greg KH
2008-10-28 5:34 ` Ananth N Mavinakayanahalli
2008-10-29 23:53 ` Greg KH
2008-10-25 21:20 ` Greg KH [this message]
2008-10-25 23:48 ` Randy Dunlap
2008-10-26 0:07 ` Randy Dunlap
2008-10-26 7:40 ` Stefan Richter
2008-10-26 8:17 ` Christoph Hellwig
2008-10-26 8:34 ` Stephen Rothwell
2008-10-26 8:39 ` Christoph Hellwig
2008-10-27 7:44 ` Lachlan McIlroy
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=20081025212037.GB32027@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).