From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Pravin Shedge <pravin.shedge4linux@gmail.com>
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
sstabellini@kernel.org, x86@kernel.org, mchehab@kernel.org,
linux-xfs@vger.kernel.org, mcgrof@kernel.org, ast@kernel.org,
shuah@kernel.org, namhyung@kernel.org, mhiramat@kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, devel@driverdev.osuosl.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] treewide: remove duplicate includes
Date: Mon, 4 Dec 2017 10:27:31 -0800 [thread overview]
Message-ID: <20171204182731.GA4903@magnolia> (raw)
In-Reply-To: <1512337779-16842-1-git-send-email-pravin.shedge4linux@gmail.com>
On Mon, Dec 04, 2017 at 03:19:39AM +0530, Pravin Shedge wrote:
> These duplicate includes have been found with scripts/checkincludes.pl but
> they have been removed manually to avoid removing false positives.
>
> Unit Testing:
>
> - build successful
> - LTP testsuite passes.
> - checkpatch.pl passes
>
> Signed-off-by: Pravin Shedge <pravin.shedge4linux@gmail.com>
<supersnip>
> diff --git a/fs/xfs/scrub/scrub.c b/fs/xfs/scrub/scrub.c
> index 9c42c4e..ab3aef2 100644
> --- a/fs/xfs/scrub/scrub.c
> +++ b/fs/xfs/scrub/scrub.c
These look reasonable, but please send me (and linux-xfs) the three
xfs changes separately so that I can add them to the xfs tree.
(Also, thank you for cc'ing the xfs list for this treewide change...)
--D
next prev parent reply other threads:[~2017-12-04 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 21:49 [PATCH] treewide: remove duplicate includes Pravin Shedge
2017-12-03 23:07 ` Luis R. Rodriguez
2017-12-03 23:20 ` Joe Perches
2017-12-04 7:38 ` Greg KH
2017-12-04 18:27 ` Darrick J. Wong [this message]
2017-12-04 19:21 ` Eduardo Valentin
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=20171204182731.GA4903@magnolia \
--to=darrick.wong@oracle.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=pravin.shedge4linux@gmail.com \
--cc=shuah@kernel.org \
--cc=sstabellini@kernel.org \
--cc=x86@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).