From: Arjan van de Ven <arjan@infradead.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Partially defer some of the async stuff to the next release
Date: Fri, 9 Jan 2009 07:09:10 -0800 [thread overview]
Message-ID: <20090109070910.233e5f3c@infradead.org> (raw)
Hi Linus,
I think it's better that we defer some of the asynchronous boot stuff to
2.6.30 so that it can bake in -next for a bit. I would like to keep the
core infrastructure in place for 29, so that the various subsystem
patches etc can just use it in -next without generating dependencies in
the patch flow.
for both libata and the inode delete very simple things can be done to
fix them, but I would feel a lot more comfortable giving these a ride
in -next.
The following changes since commit
2150edc6c5cf00f7adb54538b9ea2a3e9cedca3f: Linus Torvalds (1):
Merge branch 'for_linus' of git://git.kernel.org/.../tytso/ext4
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arjan/linux-2.6-async-undo.git
master
Arjan van de Ven (3):
Revert "fastboot: Make libata initialization even more async"
Revert "fastboot: make the libata port scan asynchronous"
partial revert of asynchronous inode delete
drivers/ata/libata-core.c | 96
+++++++++++++++++++++------------------------
fs/inode.c | 19 +++------ 2 files changed, 51
insertions(+), 64 deletions(-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next reply other threads:[~2009-01-09 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 15:09 Arjan van de Ven [this message]
2009-01-09 20:42 ` Linus Torvalds
2009-01-09 20:53 ` Arjan van de Ven
2009-01-09 21:22 ` Alan Cox
2009-01-09 21:30 ` Arjan van de Ven
2009-01-09 22:33 ` david
2009-01-09 21:54 ` Arjan van de Ven
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=20090109070910.233e5f3c@infradead.org \
--to=arjan@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome