All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] cifs: show features compiled in as part of DebugData
Date: Fri, 30 Jul 2010 22:15:07 +0530	[thread overview]
Message-ID: <4C530193.2080001@suse.de> (raw)
In-Reply-To: <AANLkTikgA8mXTcX-i3avjuQygrekicntcy3P2NBW5QuB-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 07/30/2010 08:09 PM, Steve French wrote:
> If someone ever wants a script to parse this - seems like your
> (original?) idea of putting this in /proc/fs/cifs/features instead of
> /proc/fs/cifs/DebugData (which has various other pieces of debug
> information) could be easier.

I'm not sure whether a seperate proc file for features is justified or
not.. Since the primary aim of introducing this is to faciliate
debugging and provide references in documentation etc.., looks like it
is a suitable candidate to DebugData.. but that is a matter of
preference.. Feel free to go ahead with any of these versions..

Thanks,

> On Fri, Jul 30, 2010 at 7:55 AM, Suresh Jayaraman <sjayaraman-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org> wrote:
>> Fixed the nit pointed out by Jeff.
>>
>> From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
>> Subject: [PATCH 1/2] cifs: show features compiled in as part of DebugData
>>
>> This patch adds the features that are compiled in to the CIFS debugging data
>> as shown below:
> 
> 


-- 
Suresh Jayaraman

  parent reply	other threads:[~2010-07-30 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-30 12:55 [PATCH 1/2] cifs: show features compiled in as part of DebugData Suresh Jayaraman
2010-07-30 13:04 ` Jeff Layton
2010-07-30 14:39 ` Steve French
     [not found]   ` <AANLkTikgA8mXTcX-i3avjuQygrekicntcy3P2NBW5QuB-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-30 14:57     ` Jeff Layton
     [not found]       ` <20100730105734.0827c057-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-07-30 17:53         ` Steve French
     [not found]           ` <AANLkTinyH4qiEBwtULoen8xSypaWxWCr3MQhDWf-Ftz4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-04  4:28             ` Steve French
2010-07-30 16:45     ` Suresh Jayaraman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-30 12:27 Suresh Jayaraman
2010-07-30 12:39 ` Jeff Layton

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=4C530193.2080001@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.