From: Julia Lawall <julia.lawall@inria.fr>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: cocci@inria.fr, linux-kernel@vger.kernel.org,
Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [PATCH] scripts: coccicheck: use "grep -E" instead of "egrep"
Date: Wed, 21 Sep 2022 21:26:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2209212125590.2783@hadrien> (raw)
In-Reply-To: <20220921091341.217365-1-gregkh@linuxfoundation.org>
On Wed, 21 Sep 2022, Greg Kroah-Hartman wrote:
> The latest version of grep claims that egrep is now obsolete so the build
> now contains warnings that look like:
> egrep: warning: egrep is obsolescent; using grep -E
> fix this up by moving the vdso Makefile to use "grep -E" instead.
>
> Cc: Julia Lawall <Julia.Lawall@inria.fr>
> Cc: Nicolas Palix <nicolas.palix@imag.fr>
> Cc: cocci@inria.fr
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Applied, thanks.
> ---
> scripts/coccicheck | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index caba0bff6da7..2956fce8fa4f 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -47,7 +47,7 @@ FLAGS="--very-quiet"
> # inspected there.
> #
> # --profile will not output if --very-quiet is used, so avoid it.
> -echo $SPFLAGS | egrep -e "--profile|--show-trying" 2>&1 > /dev/null
> +echo $SPFLAGS | grep -E -e "--profile|--show-trying" 2>&1 > /dev/null
> if [ $? -eq 0 ]; then
> FLAGS="--quiet"
> fi
> --
> 2.37.3
>
>
next prev parent reply other threads:[~2022-09-21 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 9:13 [PATCH] scripts: coccicheck: use "grep -E" instead of "egrep" Greg Kroah-Hartman
2022-09-21 19:26 ` Julia Lawall [this message]
2022-11-18 8:43 ` Tiezhu Yang
2022-11-20 4:48 ` [cocci] " Julia Lawall
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.2209212125590.2783@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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).