From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>,
"open list:MIPS" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] fs/seq_file.c: Rename the "Fill" label to avoid build failure
Date: Sun, 26 Apr 2020 15:46:28 +0200 [thread overview]
Message-ID: <20200426134628.GC8299@alpha.franken.de> (raw)
In-Reply-To: <CAAhV-H4obH6BS7TNJzpZvxhBo6W8qRamOh8K92rk1OaB4PxosA@mail.gmail.com>
On Sat, Apr 25, 2020 at 10:54:23AM +0800, Huacai Chen wrote:
> On Fri, Apr 24, 2020 at 7:27 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > On Fri, Apr 24, 2020 at 04:29:04PM +0800, Huacai Chen wrote:
> > > MIPS define a "Fill" macro as a cache operation in cacheops.h, this
> > > will cause build failure under some special configurations. To avoid
> > > this failure we rename the "Fill" label in seq_file.c.
> >
> > You should rename the Fill macro in the mips header instead.
> > I'd suggest Fill_R4000 of R4000_Fill.
>
> What do you think about this? If you agree to rename the "Fill" macro
> in cacheops.h, I want to rename it to Fill_I, because it has the same
> coding style as other cache operations in cacheops.h.
works for me, I've merged your patch to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-04-26 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 8:29 [PATCH] fs/seq_file.c: Rename the "Fill" label to avoid build failure Huacai Chen
2020-04-24 11:27 ` Matthew Wilcox
2020-04-25 2:54 ` Huacai Chen
2020-04-26 13:46 ` Thomas Bogendoerfer [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=20200426134628.GC8299@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.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;
as well as URLs for NNTP newsgroup(s).