From: Andrew Morton <akpm@linux-foundation.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, Steven French <sfrench@us.ibm.com>
Subject: Re: [2.6.27 patch] the scheduled smbfs removal
Date: Mon, 19 May 2008 15:32:49 -0700 [thread overview]
Message-ID: <20080519153249.ea80e683.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080519215311.GE17716@cs181133002.pp.htv.fi>
On Tue, 20 May 2008 00:53:11 +0300
Adrian Bunk <bunk@kernel.org> wrote:
> This patch contains the scheduled smbfs removal.
I don't know how popular this will be right now - quite a few
people needed to be dragged over to cifs up to a month or two
ago.
I'd suggest that we first use CONFIG_BROKEN or
CONFIG_DIFFICULT_TO_GET_AT and see what the effect of that is.
next prev parent reply other threads:[~2008-05-19 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 21:53 [2.6.27 patch] the scheduled smbfs removal Adrian Bunk
2008-05-19 22:32 ` Andrew Morton [this message]
2008-05-19 23:03 ` Steven French
2008-05-19 23:06 ` Harvey Harrison
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 0:00 Steve French
2008-05-20 0:49 ` Harvey Harrison
2008-05-20 1:49 ` Steve French
2008-05-20 2:40 ` Günter Kukkukk
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=20080519153249.ea80e683.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.