From: "Krzysztof Olędzki" <ole@ans.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.31-rc4
Date: Thu, 23 Jul 2009 19:21:07 +0200 [thread overview]
Message-ID: <4A689C03.3040508@ans.pl> (raw)
In-Reply-To: <alpine.LFD.2.01.0907221936220.3352@localhost.localdomain>
On 2009-07-23 04:44, Linus Torvalds wrote:
> Ok, that was a fun week.
>
> We had a binutils bug, a ccache bug, and a compiler bug. And that was just
> the bugs that were outside the kernel, but resulted in a broken build.
>
> But while that was unusual, the rest of the stuff is pretty regular. Lots
> of small fixes all around. The patch is dominated by a couple of new
> network drivers, but apart from those, it's generally pretty small - lots
> of one-liners and "few-liners".
>
> The shortlog gives a reasonable idea about what's happened.
>
> Linus
>
> ---
<CUT>
> Linus Torvalds (3):
> fbmon: work around compiler bug in gcc-2.4.2
Off by +2.-2.+2 error. ;)
Best regards,
Krzysztof Olędzki
prev parent reply other threads:[~2009-07-23 17:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 2:44 Linux 2.6.31-rc4 Linus Torvalds
2009-07-23 14:14 ` Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-23 14:42 ` Yinghai Lu
2009-07-23 15:57 ` Jesse Barnes
2009-07-23 14:53 ` Frans Pop
2009-07-23 16:12 ` Linus Torvalds
2009-07-23 16:29 ` Linus Torvalds
2009-07-24 4:34 ` David John
2009-07-24 5:51 ` Kind of like the following. Apply if you feel it is ok to _not_ David John
2009-07-24 7:53 ` [PATCH?] Re: Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-24 6:11 ` [PATCH] Remove Spurious PnP Memory Reserved Warning David John
2009-07-25 7:12 ` David John
2009-07-28 4:06 ` [PATCH v2] " David John
2009-07-28 16:31 ` Jesse Barnes
2009-07-29 6:42 ` David John
2009-08-01 10:56 ` Frans Pop
2009-08-06 21:41 ` Jesse Barnes
2009-07-23 17:21 ` Krzysztof Olędzki [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=4A689C03.3040508@ans.pl \
--to=ole@ans.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