public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Steve French <smfrench@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org
Subject: Re: SMB2 file system - should it be a distinct module
Date: Tue, 1 May 2007 10:06:57 +0100	[thread overview]
Message-ID: <20070501090657.GA17949@infradead.org> (raw)
In-Reply-To: <524f69650704301552j13cd46e5y53a233af753e0548@mail.gmail.com>

On Mon, Apr 30, 2007 at 05:52:43PM -0500, Steve French wrote:
> Any idea which would be preferred (smb2 support as part of cifs, or as
> a distinct smb2.ko module)?

Separate module please.  If we grow enough common code as some point
we can move it into a smb_common.ko helper library, but given your
above description I doubt that would useful.


  parent reply	other threads:[~2007-05-01  9:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 22:52 SMB2 file system - should it be a distinct module Steve French
2007-04-30 23:15 ` Chris Friesen
2007-05-01  9:06 ` Christoph Hellwig [this message]
2007-05-03 13:21   ` [linux-cifs-client] " simo
2007-05-03 14:17     ` Christoph Hellwig
2007-05-03 14:36       ` simo
2007-05-03 14:43         ` Christoph Hellwig
2007-05-03 14:53           ` simo
2007-05-03 15:14           ` Chuck Ebbert
2007-05-03 14:46         ` Gerald Carter
2007-05-03 14:56           ` simo
2007-05-03 15:35             ` Steve French
2007-05-03 15:44               ` Christoph Hellwig
2007-05-04 17:12           ` Jeremy Allison
2007-05-04 17:43             ` simo
2007-05-05  9:55               ` Christoph Hellwig
2007-05-04 18:35             ` Steve French
2007-05-01  9:30 ` Jan Engelhardt
2007-05-01 19:26   ` [linux-cifs-client] Re: SMB2 file system - should it be a distinctmodule Wagner, Chris (GEAE, CBTS)

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=20070501090657.GA17949@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox