All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Christopher Sacchi <chris.sacchi@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: BeFs parser.h support in linux kernel v3.5
Date: Mon, 06 Aug 2012 17:48:23 -0700	[thread overview]
Message-ID: <502065D7.3020704@xenotime.net> (raw)
In-Reply-To: <CAGh4K3+krr7Zy97VeFm80U3xsidaWwHLWcbKb-WZ4x+3vH4Sug@mail.gmail.com>

On 08/06/2012 05:07 PM, Christopher Sacchi wrote:

> This patch adds a new header, in the to-do list. There are no style issues.
> Here's the patch:
> --
> Signed-off-by: Christopher P. Sacchi <chris.sacchi@gmail.com>
> --- befs.h      2012-07-21 20:58:29.000000000 +0000
> +++ befs.h      2012-08-06 19:52:05.000000000 +0000
> @@ -9,6 +9,7 @@
>  #define _LINUX_BEFS_H
> 
>  #include "befs_fs_types.h"
> +#include "linux-3.5/include/parser.h"
> 
>  /* used in debug.c */
>  #define BEFS_VERSION "0.9.3"
> 
> --


filesystem patches should also go to linux-fsdevel@vger.kernel.org .


from TODO file:
* See if Alexander Viro's option parser made it into the kernel tree. 
	Use that if we can. (include/linux/parser.h)

Yes, the option parser made it into the kernel tree several years ago,
but just adding the header doesn't make befs use the option parser,
so the patch is not enough.  And the header patch should be:

#include <linux/parser.h>



-- 
~Randy

      reply	other threads:[~2012-08-07  0:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  0:07 [PATCH]: BeFs parser.h support in linux kernel v3.5 Christopher Sacchi
2012-08-07  0:48 ` Randy Dunlap [this message]

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=502065D7.3020704@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=chris.sacchi@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 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.