From: Linus Torvalds <torvalds@linux-foundation.org>
To: dedekind1@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.6-rc1
Date: Fri, 3 Aug 2012 13:23:29 -0700 [thread overview]
Message-ID: <CA+55aFz322dKXUwtmrrW=nfp5XJa5ACh1syE8RXOOdcA7V_76A@mail.gmail.com> (raw)
In-Reply-To: <1343976472.1730.18.camel@sauron.fi.intel.com>
On Thu, Aug 2, 2012 at 11:47 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> We have had 11 of 13 pieces of the 'sync_supers()' removal patch-sets
> merged. The 12th piece removes dead code in exofs was supposed to go
> through the exofs tree and blocked the 13th piece which removes
> 'sync_supers()' and was supposed to go via the VFS tree.
>
> Both 12th and 13th pieces zap dead code. I man not sure delaying that to
> v3.7 would be very beneficial for the kernel (why having a useless
> thread waking up every 5 secs?). Would you let us merge this to -rc1?
Ok. I'm pulling the exofs changes, they're small and remove more lines
than they add. And if the last piece then just kills dead code, I
won't mind that either.
Linus
next prev parent reply other threads:[~2012-08-03 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 1:17 Linux 3.6-rc1 Linus Torvalds
2012-08-03 6:47 ` Artem Bityutskiy
2012-08-03 20:23 ` Linus Torvalds [this message]
2012-08-04 4:46 ` Al Viro
2012-08-04 5:38 ` Artem Bityutskiy
2012-08-04 6:19 ` Al Viro
2012-08-04 7:51 ` Dongsheng Song
2012-08-04 8:19 ` Al Viro
2012-08-04 5:43 ` Artem Bityutskiy
2012-08-03 19:01 ` Nicholas A. Bellinger
2012-08-04 0:02 ` [PATCH] pstore: fix printk format warning Randy Dunlap
2012-08-04 1:15 ` Anton Vorontsov
2012-08-04 1:32 ` Randy Dunlap
2012-08-04 1:35 ` Kees Cook
2012-08-06 16:07 ` Luck, Tony
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+55aFz322dKXUwtmrrW=nfp5XJa5ACh1syE8RXOOdcA7V_76A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).