From: Rodolfo Giometti <giometti@enneenne.com>
To: Matt Ranostay <matt.ranostay@konsulko.com>, linux-kernel@vger.kernel.org
Cc: Rodolfo Giometti <giometti@enneenne.com>,
Moritz Fischer <mdf@kernel.org>,
George McCollister <george.mccollister@gmail.com>
Subject: Re: [PATCH 1/2] pps: add ioctl_compat function to correct ioctl definitions
Date: Sat, 4 Mar 2017 08:26:47 +0100 [thread overview]
Message-ID: <f272540a-d1b7-5488-b4e4-6abdfeb5c2ae@enneenne.com> (raw)
In-Reply-To: <20170224202347.11944-2-matt.ranostay@konsulko.com>
On 02/24/17 21:23, Matt Ranostay wrote:
> ioctl definitions use the pointer size of the architecture which
> is fine when userspace and kernel are the same bitsize. This
> patchset workarounds an issue with mixed bitsize kernel + userspace
> by rewriting the cmd to the kernelspace architecture pointer size.
>
> Cc: Rodolfo Giometti <giometti@enneenne.com>
> Cc: Moritz Fischer <mdf@kernel.org>
> Cc: George McCollister <george.mccollister@gmail.com>
> Signed-off-by: Matt Ranostay <matt.ranostay@konsulko.com>
> ---
> drivers/pps/pps.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
--
HCE Engineering e-mail: giometti@hce-engineering.com
GNU/Linux Solutions giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
Cosino Project - the quick prototyping embedded system - www.cosino.io
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
next prev parent reply other threads:[~2017-03-04 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 20:23 [PATCH 0/2] pps: add ioctl_compat support Matt Ranostay
2017-02-24 20:23 ` [PATCH 1/2] pps: add ioctl_compat function to correct ioctl definitions Matt Ranostay
2017-03-04 7:26 ` Rodolfo Giometti [this message]
2017-02-24 20:23 ` [PATCH 2/2] pps: fix padding issue with PPS_FETCH for ioctl_compat Matt Ranostay
2017-03-04 7:32 ` Rodolfo Giometti
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=f272540a-d1b7-5488-b4e4-6abdfeb5c2ae@enneenne.com \
--to=giometti@enneenne.com \
--cc=george.mccollister@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.ranostay@konsulko.com \
--cc=mdf@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
all inboxes | Powered by JetHome®