All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: nick <xerofoify@gmail.com>
Cc: clm@fb.com, jbacik@fb.com, paulmck@linux.vnet.ibm.com,
	josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, laijs@cn.fujitsu.com,
	linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: How to do Header Dependency  Check Properly for Kernel Patch
Date: Fri, 27 Mar 2015 17:44:05 +0100	[thread overview]
Message-ID: <20150327164405.GA5758@suse.cz> (raw)
In-Reply-To: <55149A03.4040807@gmail.com>

On Thu, Mar 26, 2015 at 07:45:07PM -0400, nick wrote:
> I have a patch for moving over the rcu-string header file for btrfs to
> the standard include headers in include/linux
> as you stated this on a to do on the brtfs to do page for the
> project's wiki page.

The wiki page states that the task is already assigned
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Move_rcu_string_out_of_btrfs_to_lib.2F

besides that there were 8 iterations of the patchset, acked by the
respective people.

http://thread.gmane.org/gmane.linux.kernel/1862689

> index de5e4f2..df8e981 100644
> --- a/fs/btrfs/btrfs_inode.h
> +++ b/fs/btrfs/btrfs_inode.h
> @@ -15,11 +15,13 @@
>   * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
>   * Boston, MA 021110-1307, USA.
>   */
> +#pragma once
>  
>  #ifndef __BTRFS_I__
>  #define __BTRFS_I__

the pragmas are not used in kernel AFAIK, the ifndef right below the
line serves the exact purpose.

           reply	other threads:[~2015-03-27 16:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <55149A03.4040807@gmail.com>]

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=20150327164405.GA5758@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=xerofoify@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 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.