From: Rong Chen <rong.a.chen@intel.com>
To: Dave Chinner <david@fromorbit.com>, kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-xfs@vger.kernel.org
Subject: Re: [kbuild-all] Re: [dgc-xfs:xfs-async-inode-reclaim 28/30] fs/xfs/xfs_inode.c:3432:1: warning: no previous prototype for 'xfs_iflush'
Date: Thu, 28 May 2020 16:51:34 +0800 [thread overview]
Message-ID: <a044ccc9-d83b-8a96-81b5-9aaad952387f@intel.com> (raw)
In-Reply-To: <20200526221643.GZ2040@dread.disaster.area>
On 5/27/20 6:16 AM, Dave Chinner wrote:
> On Tue, May 26, 2020 at 07:46:45PM +0800, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git xfs-async-inode-reclaim
> Hiya kbuild robot!
>
> Can you drop all the list cc's from build failures for this repo?
> Nobody but me really needs to see all the breakage in this tree...
Hi Dave,
Thanks for the feedback, we have marked the repo as private:
https://github.com/intel/lkp-tests/blob/master/repo/linux/dgc-xfs
>
>> :::::: The code at line 3432 was first introduced by commit
>> :::::: 30ebf34422da6206608b0c6fba84b424f174b8c5 xfs: rename xfs_iflush_int()
>>
>> :::::: TO: Dave Chinner <dchinner@redhat.com>
>> :::::: CC: Dave Chinner <david@fromorbit.com>
> Also, I don't think this is doing what you expect, either, because
> this build error was only sent to david@fromorbit.com and was not
> CC'd to the author of the commit which is dchinner@redhat.com....
We have fixed it to avoid force changing "Dave Chinner" to "Dave Chinner
<david@fromorbit.com>".
Best Regards,
Rong Chen
>
> Cheers,
>
> Dave.
prev parent reply other threads:[~2020-05-28 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 11:46 [dgc-xfs:xfs-async-inode-reclaim 28/30] fs/xfs/xfs_inode.c:3432:1: warning: no previous prototype for 'xfs_iflush' kbuild test robot
2020-05-26 22:16 ` Dave Chinner
2020-05-28 8:51 ` Rong Chen [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=a044ccc9-d83b-8a96-81b5-9aaad952387f@intel.com \
--to=rong.a.chen@intel.com \
--cc=david@fromorbit.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.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