From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: vincenzo.frascino@arm.com, linux-kernel@vger.kernel.org,
luto@kernel.org, tglx@linutronix.de,
Andrew Morton <akpm@linux-foundation.org>,
Julia Lawall <Julia.Lawall@inria.fr>
Subject: Re: [PATCH] lib/vdso: use "grep -E" instead of "egrep"
Date: Mon, 21 Nov 2022 11:39:04 +0800 [thread overview]
Message-ID: <e66712fd-bf28-08b6-8f2f-18d8a9a3a159@loongson.cn> (raw)
In-Reply-To: <337a9a23-436e-7f58-bfc5-600452779472@loongson.cn>
Hi all,
Just FYI.
On 11/19/2022 09:54 AM, Tiezhu Yang wrote:
> Cc Andrew Morton <akpm@linux-foundation.org>
>
> On 11/18/2022 05:12 PM, Greg KH wrote:
>> On Fri, Nov 18, 2022 at 04:44:50PM +0800, Tiezhu Yang wrote:
>>> Hi,
>>>
>>> This patch can not be found in the torvalds/linux.git or
>>> next/linux-next.git tree, please take a look, thank you.
>>
>> That is because no one has applied it to their trees :(
>>
>
> Maybe Andrew can pick the following two patches sent by Greg.
>
> [PATCH] lib/vdso: use "grep -E" instead of "egrep"
> https://lore.kernel.org/lkml/20220920170633.3133829-1-gregkh@linuxfoundation.org/
>
AFAIK, this patch is not in any tree now.
>
> [PATCH] scripts: coccicheck: use "grep -E" instead of "egrep"
> https://lore.kernel.org/lkml/20220921091341.217365-1-gregkh@linuxfoundation.org/
>
This patch is in the following tree, sorry for missing that.
https://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux.git/commit/?h=for-6.1&id=2d63e6a3d971
Thanks,
Tiezhu
prev parent reply other threads:[~2022-11-21 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:06 [PATCH] lib/vdso: use "grep -E" instead of "egrep" Greg Kroah-Hartman
2022-09-21 9:44 ` Vincenzo Frascino
2022-11-18 8:44 ` Tiezhu Yang
2022-11-18 9:12 ` Greg KH
2022-11-19 1:54 ` Tiezhu Yang
2022-11-21 3:39 ` Tiezhu Yang [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=e66712fd-bf28-08b6-8f2f-18d8a9a3a159@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.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).