From: Andrew Morton <akpm@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org, "Brown,
Len" <len.brown@intel.com>, David Woodhouse <dwmw2@infradead.org>,
Jens Axboe <axboe@suse.de>, Steven French <sfrench@us.ibm.com>,
Roland Dreier <rolandd@cisco.com>,
Wim Van Sebroeck <wim@iguana.be>,
Anton Altaparmakov <aia21@cantab.net>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: git status (was: drm tree for 2.6.16-rc1)
Date: Thu, 12 Jan 2006 13:42:55 -0800 [thread overview]
Message-ID: <20060112134255.29074831.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0601121016020.3535@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
>
>
> On Thu, 12 Jan 2006, Dave Airlie wrote:
> >
> > Hi Linus,
> > Can you pull the drm-forlinus branch from
> > git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
> >
> > This is a pretty major merge over of DRM CVS, and every driver in the DRM
> > is brought up to latest versions....
>
> I'm actually somewhat inclined to not pull any more. We've had lots of
> (hopefully minor) issues for the last few days, and I know that people
> had DRM issues with the -mm tree (which I assume tracked this tree) not
> more than a week or so ago.
iirc that was AGP. DRM had a few won't-compile problems, now fixed.
So I think we could squeeze DRM in, but yes, it's getting to that time.
> IOW, I want to make sure that my tree is somewhat stable again. I don't
> want -rc1 to be horrible.
Merge status:
Size in bytes tree
(including changlog)
666832 git-acpi.patch
2534 git-agpgart.patch
98909 git-audit.patch
32930 git-cfq.patch
46766 git-cifs.patch
289519 git-drm.patch
465768 git-infiniband.patch
1045 git-ntfs.patch
9244 git-ocfs2.patch
40442 git-pcmcia.patch
24191 git-sym2.patch
31765 git-watchdog.patch
acpi: A few recent reports of AML-level unaligned accesses in that tree.
audit: we're tracking one oops which seems to be coming out of the audit code
cfq: OK
CIFS: no problems of which I'm aware
DRM: no problems of which I'm aware
infiniband: Roland, you need to resend the pull request asap, please.
ntfs: no problems of which I'm aware
ocfs2: it's a small update
pcmcia: had a problem but I think that's now fixed. But this seems
to be fairly fresh code?
sym2: no problems of which I'm aware
watchdog: Wim has been very quiet in recent months. No problems
of which I'm aware.
next prev parent reply other threads:[~2006-01-12 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 9:52 [git tree] drm tree for 2.6.16-rc1 Dave Airlie
2006-01-12 18:17 ` Linus Torvalds
2006-01-12 20:33 ` Dave Airlie
2006-01-12 21:52 ` Linus Torvalds
2006-01-12 21:42 ` Andrew Morton [this message]
2006-01-12 21:55 ` git status (was: drm tree for 2.6.16-rc1) Dominik Brodowski
2006-01-12 21:55 ` David Woodhouse
2006-01-12 22:07 ` Andrew Morton
2006-01-12 22:57 ` David Woodhouse
2006-01-12 22:07 ` git status Roland Dreier
2006-01-12 22:11 ` git status (was: drm tree for 2.6.16-rc1) Dmitry Torokhov
2006-01-15 9:55 ` Wim Van Sebroeck
2006-01-12 22:55 ` Stuff left for 2.6.16-rc1 (was: [git tree] " Russell King
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=20060112134255.29074831.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cantab.net \
--cc=airlied@linux.ie \
--cc=axboe@suse.de \
--cc=dwmw2@infradead.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rolandd@cisco.com \
--cc=sfrench@us.ibm.com \
--cc=torvalds@osdl.org \
--cc=wim@iguana.be \
/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