From: Julia Lawall <julia.lawall@inria.fr>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Denis Efremov <efremov@linux.com>,
kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [kbuild-all] Re: [PATCH] arm64: cpufeatures: use min and max
Date: Fri, 30 Apr 2021 19:40:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2104301939120.13185@hadrien> (raw)
In-Reply-To: <20210430173818.GF18574@arm.com>
On Fri, 30 Apr 2021, Catalin Marinas wrote:
> Hi Julia,
>
> On Thu, Apr 29, 2021 at 10:50:46PM +0200, Julia Lawall wrote:
> > From: kernel test robot <lkp@intel.com>
> >
> > Use min and max to make the effect more clear.
> >
> > Generated by: scripts/coccinelle/misc/minmax.cocci
> >
> > Fixes: 8636e3295ce3 ("coccinelle: misc: add minmax script")
>
> What's with this Fixes tag? I can't find it anywhere and I don't think
> it warrants such a tag anyway, it's not a bug.
>
> I'll apply it without the tag and include minmax.h as per Mark's
> comment.
Oops, sorry about that. It's something that 0-day adds, but I think it is
always incorrect for new semantic patches. Please remove it.
thanks,
julia
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-30 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 20:50 [PATCH] arm64: cpufeatures: use min and max Julia Lawall
2021-04-30 11:49 ` Mark Rutland
2021-04-30 17:38 ` Catalin Marinas
2021-04-30 17:40 ` Julia Lawall [this message]
2021-04-30 17:56 ` Catalin Marinas
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=alpine.DEB.2.22.394.2104301939120.13185@hadrien \
--to=julia.lawall@inria.fr \
--cc=amit.kachhap@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=efremov@linux.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@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