From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ZhangXiaoxu <zhangxiaoxu5@huawei.com>
Subject: Re: linux-next: Fixes tags need some work in the cifs tree
Date: Tue, 9 Apr 2019 09:54:49 +1000 [thread overview]
Message-ID: <20190409095449.72007f57@canb.auug.org.au> (raw)
In-Reply-To: <CAH2r5mvSQ6+gq92EMtj+_DYCZW_AOjZocJ9rAKHdtU09Nw-pgw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 624 bytes --]
Hi Steve,
On Mon, 8 Apr 2019 17:30:20 -0500 Steve French <smfrench@gmail.com> wrote:
>
> I just fixed these up manually and repushed to cifs-2.6.git for-next
Thanks.
> I was curious if checkpatch should have flagged this - I reran
> checkpatch on the original version of Zhang's patches and it didn't
> complain about the spacing (and probably should have).
Yeah, I use the attached script to check for these. I was hoping that
someone might hack at least some of theses tests into checkpatch, but
that hasn't happened yet :-( But, then again, I don't run checkpatch :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: check_fixes --]
[-- Type: application/x-shellscript, Size: 4344 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-04-08 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 21:38 linux-next: Fixes tags need some work in the cifs tree Stephen Rothwell
2019-04-08 22:30 ` Steve French
2019-04-08 23:54 ` Stephen Rothwell [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=20190409095449.72007f57@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=zhangxiaoxu5@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