From: Guillaume Nault <g.nault@alphalink•fr>
To: Arnd Bergmann <arnd@arndb•de>
Cc: paulus@samba•org, linux-ppp@vger•kernel.org,
netdev@vger•kernel.org, mitch@sfgoth•com, mostrows@earthlink•net,
jchapman@katalix•com, xeb@mail•ru, davem@davemloft•net,
viro@zeniv•linux.org.uk, y2038@lists•linaro.org,
linux-kernel@vger•kernel.org, Kirill Tkhai <ktkhai@virtuozzo•com>
Subject: Re: [PATCH net-next 3/5] ppp: move PPPIOCSCOMPRESS32 to ppp-generic.c
Date: Thu, 30 Aug 2018 13:04:59 +0200 [thread overview]
Message-ID: <20180830110459.GA19111@alphalink.fr> (raw)
In-Reply-To: <20180829140409.833488-3-arnd@arndb.de>
On Wed, Aug 29, 2018 at 04:03:28PM +0200, Arnd Bergmann wrote:
> PPPIOCSCOMPRESS is only implemented in ppp_generic, so it's best to move
> the compat handling there. My first approach was to keep it in a new
> ppp_compat_ioctl() function, but it turned out to be much simpler to do
> it in the regular ioctl handler, by allowing both structure layouts to
> be handled directly there.
>
Acked-by: Guillaume Nault <g.nault@alphalink•fr>
next prev parent reply other threads:[~2018-08-30 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:03 [PATCH net-next 1/5] pppoe: fix PPPOEIOCSFWD compat handling Arnd Bergmann
2018-08-29 14:03 ` [PATCH net-next 2/5] ppp: move simple ioctl compat handling out of fs_compat_ioctl.c Arnd Bergmann
2018-08-29 14:03 ` [PATCH net-next 3/5] ppp: move PPPIOCSCOMPRESS32 to ppp-generic.c Arnd Bergmann
2018-08-30 11:04 ` Guillaume Nault [this message]
2018-08-29 14:03 ` [PATCH net-next 4/5] ppp: move PPPIOCSPASS32/PPPIOCSACTIVE32 to ppp_generic.c Arnd Bergmann
2018-08-30 11:05 ` Guillaume Nault
2018-08-29 14:03 ` [PATCH net-next 5/5] ppp: handle PPPIOCGIDLE for 64-bit time_t Arnd Bergmann
2018-08-30 11:06 ` Guillaume Nault
2018-08-30 11:47 ` Arnd Bergmann
2018-08-30 11:04 ` [PATCH net-next 1/5] pppoe: fix PPPOEIOCSFWD compat handling Guillaume Nault
2018-08-30 11:54 ` Arnd Bergmann
2018-08-30 13:09 ` Guillaume Nault
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=20180830110459.GA19111@alphalink.fr \
--to=g.nault@alphalink$(echo .)fr \
--cc=arnd@arndb$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=jchapman@katalix$(echo .)com \
--cc=ktkhai@virtuozzo$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-ppp@vger$(echo .)kernel.org \
--cc=mitch@sfgoth$(echo .)com \
--cc=mostrows@earthlink$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulus@samba$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=xeb@mail$(echo .)ru \
--cc=y2038@lists$(echo .)linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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