linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Guo Zhengkui <guozhengkui@vivo.com>
Cc: Jan Kara <jack@suse.com>,
	"open list:EXT2 FILE SYSTEM" <linux-ext4@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	kernel@vivo.com
Subject: Re: [PATCH] fs: ext2: remove duplicate includes
Date: Mon, 13 Dec 2021 14:24:59 +0100	[thread overview]
Message-ID: <20211213132459.GA14044@quack2.suse.cz> (raw)
In-Reply-To: <20211207085525.4390-1-guozhengkui@vivo.com>

On Tue 07-12-21 16:55:24, Guo Zhengkui wrote:
> remove a duplicate "#include <linux/dax.h>"
> 
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>

Thanks for the patch. Which kernel is it based on? Because I don't see the
duplicate line in my tree...

								Honza

> ---
>  fs/ext2/inode.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c
> index 602578b72d8c..da4c301b4305 100644
> --- a/fs/ext2/inode.c
> +++ b/fs/ext2/inode.c
> @@ -29,21 +29,20 @@
>  #include <linux/dax.h>
>  #include <linux/blkdev.h>
>  #include <linux/quotaops.h>
>  #include <linux/writeback.h>
>  #include <linux/buffer_head.h>
>  #include <linux/mpage.h>
>  #include <linux/fiemap.h>
>  #include <linux/iomap.h>
>  #include <linux/namei.h>
>  #include <linux/uio.h>
> -#include <linux/dax.h>
>  #include "ext2.h"
>  #include "acl.h"
>  #include "xattr.h"
>  
>  static int __ext2_write_inode(struct inode *inode, int do_sync);
>  
>  /*
>   * Test whether an inode is a fast symlink.
>   */
>  static inline int ext2_inode_is_fast_symlink(struct inode *inode)
> -- 
> 2.20.1
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2021-12-13 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  8:55 [PATCH] fs: ext2: remove duplicate includes Guo Zhengkui
2021-12-13 13:24 ` Jan Kara [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=20211213132459.GA14044@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=guozhengkui@vivo.com \
    --cc=jack@suse.com \
    --cc=kernel@vivo.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).