From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Zubair Lutfullah Kakakhel
<Zubair.Kakakhel-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv2] vdso.7: update for MIPS
Date: Tue, 12 Apr 2016 22:08:28 -0400 [thread overview]
Message-ID: <20160413020828.GD6588@vapier.lan> (raw)
In-Reply-To: <1460448781-42861-1-git-send-email-Zubair.Kakakhel-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On 12 Apr 2016 09:13, Zubair Lutfullah Kakakhel wrote:
> +__kernel_rt_sigreturn LINUX_2.6 (exported since Linux 4.4)
> +__kernel_sigreturn LINUX_2.6 (exported since Linux 4.4)
are these actually exported ? looking at vdso.lds.S, only the other two
are. my question previously was more about the kernel behavior than it
was about the docs being incorrect. your v1 looks fine to merge now (as
the 4.4 release is already out the door).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-13 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 15:24 [PATCH] vdso.7: update for MIPS Zubair Lutfullah Kakakhel
[not found] ` <1459869874-61625-1-git-send-email-Zubair.Kakakhel-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2016-04-06 19:01 ` Mike Frysinger
[not found] ` <20160406190137.GH6588-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-04-12 8:13 ` [PATCHv2] " Zubair Lutfullah Kakakhel
[not found] ` <1460448781-42861-1-git-send-email-Zubair.Kakakhel-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2016-04-13 2:08 ` Mike Frysinger [this message]
[not found] ` <20160413020828.GD6588-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-04-18 13:15 ` Michael Kerrisk (man-pages)
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=20160413020828.GD6588@vapier.lan \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=Zubair.Kakakhel-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).