From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
cpufreq@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 10
Date: Wed, 10 Apr 2013 12:40:32 +0200 [thread overview]
Message-ID: <CA+icZUWYHv5h26Q6xr30=UxavD52ZX6W1vfTKj8n6gyuCz0q3g@mail.gmail.com> (raw)
In-Reply-To: <20130410184852.92a3a02bbe5c3a040be76365@canb.auug.org.au>
On Wed, Apr 10, 2013 at 10:48 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130409:
>
> The vfs tree lost its build failure.
>
Beyond build-failures in vfs-next [0] and [1], it was not bootable
(see [2] till [4])!
This is now all fixed, thanks to all involved people!
$ cat /proc/version
Linux version 3.9.0-rc6-next20130410-1-iniza-small
(sedat.dilek@gmail.com@fambox) (gcc version 4.6.3 (Ubuntu/Linaro
4.6.3-1ubuntu5) ) #1 SMP Wed Apr 10 11:55:58 CEST 2013
NOTE: There still exists the NULL-pointer-deref in cpufreq for me on
Intel SandyBridge CPU (see [5]) on reboot and when CPUs get offline.
- Sedat -
[0] https://lkml.org/lkml/2013/4/7/229
[1] http://marc.info/?l=linux-next&m=136552249527170&w=2
[2] http://marc.info/?t=136545773000008&r=1&w=2
[3] http://marc.info/?t=136545603700003&r=1&w=2
[4] http://marc.info/?l=linux-next&m=136552718229123&w=2
[5] http://marc.info/?t=136551588400003&r=1&w=2
next prev parent reply other threads:[~2013-04-10 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 8:48 linux-next: Tree for Apr 10 Stephen Rothwell
2013-04-10 10:40 ` Sedat Dilek [this message]
2013-04-10 21:36 ` linux-next: Tree for Apr 10 (meda and OF) Randy Dunlap
2013-04-10 22:00 ` linux-next: Tree for Apr 10 (media " Sylwester Nawrocki
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 4:53 linux-next: Tree for Apr 10 Stephen Rothwell
2020-04-10 3:27 Stephen Rothwell
2019-04-10 6:30 Stephen Rothwell
2018-04-10 4:51 Stephen Rothwell
2017-04-10 7:52 Stephen Rothwell
2015-04-10 11:18 Stephen Rothwell
2014-04-10 4:50 Stephen Rothwell
2012-04-10 4:55 Stephen Rothwell
2012-04-10 5:12 ` Stephen Rothwell
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='CA+icZUWYHv5h26Q6xr30=UxavD52ZX6W1vfTKj8n6gyuCz0q3g@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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).