From: Alejandro Colomar <alx.manpages@gmail.com>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] vdso.7: fix risc-v symbol names.
Date: Wed, 1 Feb 2023 00:59:13 +0100 [thread overview]
Message-ID: <9b541acf-4522-a74e-d3b7-bcdea6c8aded@gmail.com> (raw)
In-Reply-To: <CAJgzZooXi8G=Ega2VN26KGBC7pKknRAW6E1tWXYr81_Dx2BZgA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
Hi Elliott,
On 1/31/23 18:39, enh wrote:
> On Tue, Jan 31, 2023 at 4:52 AM Alejandro Colomar
> <alx.manpages@gmail.com> wrote:
>>
>> Hi!
>>
>> On 1/31/23 00:02, enh wrote:
>>> The kernel git history says the names have always been "__vdso_" rather
>>> than "__kernel_", so I assume this was a copy & paste mistake from a
>>> different architecture.
>>>
>>> Luckily, the path to the kernel source that lets you confirm/deny this
>>> _is_ correct :-)
>>
>> Could you please sign the patch?
>
> done.
Patch applied. Thanks!
> (i did read that part of the docs, but assumed this counted as a
> "trivial" patch :-) )
:-)
>
>>
>> Also, it seems something is broken in the patch; maybe the mailer broke it? I
>> can't seem to apply it. Please check.
>
> ugh, yeah, gmail and tabs really don't get on, and this file is full
> of tabs. trying again as an attachment...
Heh :) Any hopes that you can suggest google brings back full plain text
support? :P
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-31 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 23:02 [PATCH] vdso.7: fix risc-v symbol names enh
2023-01-31 12:51 ` Alejandro Colomar
2023-01-31 17:39 ` enh
2023-01-31 23:59 ` Alejandro Colomar [this message]
2023-02-01 19:39 ` enh
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=9b541acf-4522-a74e-d3b7-bcdea6c8aded@gmail.com \
--to=alx.manpages@gmail.com \
--cc=enh@google.com \
--cc=linux-man@vger.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