mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <gaoxiang25@huawei.com>
To: 김성경 <jotun9935@gmail.com>
Cc: <yuchao0@huawei.com>, <gregkh@linuxfoundation.org>,
	<linux-erofs@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<devel@driverdev.osuosl.org>
Subject: Re: [PATCH] staging: erofs: Add a blank line after declarations
Date: Thu, 13 Dec 2018 11:42:56 +0800	[thread overview]
Message-ID: <f782280e-79a4-87a7-bf98-d95c895f2a85@huawei.com> (raw)
In-Reply-To: <CAHw2A4mmtktjnb3rrWF3x4B-Hn1mq3sCZkXNmsQ+Gi=_tiH3=w@mail.gmail.com>



On 2018/12/13 11:29, 김성경 wrote:
> Thank you. I appreciate it for your prompt reply.
> 
> 
> As a result of checking through 'checkpatch.pl <http://checkpatch.pl>', there was only one coding style problem in 'erofs / inode.c' file.
> 
> 
> I will check for other files and send the patch file soon.

Yes, if you confirm that this is the only one place, I think this patch is ok for me personally. :)

Thanks,
Gao Xiang

> 
> 
> Thanks,
> 
> Sungkyung Kim 
> 
> 
> 2018년 12월 13일 (목) 오전 10:51, Gao Xiang <gaoxiang25@huawei.com <mailto:gaoxiang25@huawei.com>>님이 작성:
> 
>     Hi Sungkyung,
> 
>     On 2018/12/12 23:50, Sungkyung Kim wrote:
>     > Fix a warning from checkpathch.pl <http://checkpathch.pl>: 'Missing a blank line after
>     > declarations'
>     >
>     > Signed-off-by: Sungkyung Kim <jotun9935@gmail.com <mailto:jotun9935@gmail.com>>
>     > ---
>     >  drivers/staging/erofs/inode.c | 1 +
>     >  1 file changed, 1 insertion(+)
>     >
>     > diff --git a/drivers/staging/erofs/inode.c b/drivers/staging/erofs/inode.c
>     > index 04c61a9d7b76..82b6ad5badff 100644
>     > --- a/drivers/staging/erofs/inode.c
>     > +++ b/drivers/staging/erofs/inode.c
>     > @@ -278,6 +278,7 @@ struct inode *erofs_iget(struct super_block *sb,
>     >       if (inode->i_state & I_NEW) {
>     >               int err;
>     >               struct erofs_vnode *vi = EROFS_V(inode);
>     > +
> 
>     Thanks for your patch, is there a only one 'Missing a blank line after declarations' in erofs?
> 
>     If not, could you have time check the other files? That is my personal thought, and
>     I cc-ed the staging mailing list as well.
> 
>     Thanks,
>     Gao Xiang
> 
>     >               vi->nid = nid;
>     > 
>     >               err = fill_inode(inode, isdir);
>     >
> 

  parent reply	other threads:[~2018-12-13  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181212155023.45294-1-jotun9935@gmail.com>
2018-12-13  1:51 ` Gao Xiang
     [not found]   ` <CAHw2A4mmtktjnb3rrWF3x4B-Hn1mq3sCZkXNmsQ+Gi=_tiH3=w@mail.gmail.com>
2018-12-13  3:42     ` Gao Xiang [this message]
2018-12-13 10:34   ` Chao Yu

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=f782280e-79a4-87a7-bf98-d95c895f2a85@huawei.com \
    --to=gaoxiang25@huawei.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jotun9935@gmail.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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

all inboxes | Powered by JetHome®