From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.30-rc6
Date: Sat, 16 May 2009 22:35:43 +0200 [thread overview]
Message-ID: <200905162235.43670.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.01.0905152120140.3301@localhost.localdomain>
On Saturday 16 May 2009, Linus Torvalds wrote:
>
> Another week, another -rc.
>
> Things definitely are calming down, with just about 300 commits in the
> last week. And most of them are pretty small too, although the powerpc
> updates brought some defconfig changes that look largish.
>
> Somewhat unusually, the dirstat shows filesystems with as much changes as
> drivers - we had some nilfs2 and reiserfs updates there, along with some
> mostly trivial vfs layer cleanups. We had a BKL pushdown in the umount
> paths, for example (that will hopefully make it easier to then merge the
> BKL removal patches for reiserfs during the next merge window).
>
> On the arch side, apart from the powerpc things, we have soem cris and
> MIPS updates. The bulk of the cris updates was merging the compressed boot
> code across chris-v10 and chris-v32, so the diffs there look bigger than
> they really were.
>
> On the driver front, there's some sata updates, some i915 graphics
> updates, and various other small things sprinkled all over. Some sound
> driver updates too, although most of those seem to be the davinci stuff
> (from the arm merge last -rc), so most people won't notice or care.
>
> And we've hopefully fixed a number of regressions. Please remind people
> (me very much included) of all the ones that you still see - I've been
> missing Rafael's regular regression summaries ;(
Well, you've taken me by surprise with this -rc, I'm going to send the list later
today or tomorrow.
To be honest, I have a problem with people not notifying me when their bugs get
fixed or when there are patches available. As a result I have to dig into the
email threads or look into the Bugzilla entries to check whether or not I
should close them. This takes a lot of time.
It would be much easier to me if people told me when to update the bug entries
or, even better, if they updated the bug entries themselves (if possible).
Thanks,
Rafael
prev parent reply other threads:[~2009-05-16 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 4:36 Linux 2.6.30-rc6 Linus Torvalds
2009-05-16 6:53 ` Jeff Garzik
2009-05-16 8:48 ` setlocalversion bug [Was: Linux 2.6.30-rc6] Sam Ravnborg
2009-05-16 9:58 ` Nico Schottelius
2009-05-16 12:00 ` Nico Schottelius
2009-05-16 11:23 ` Linux 2.6.30-rc6 Alejandro Riveira Fernández
2009-05-16 20:35 ` Rafael J. Wysocki [this message]
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=200905162235.43670.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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