From: Yann Droneaud <ydroneaud@opteya.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 8/8] industrialio: use anon_inode_getfd() with O_CLOEXEC flag
Date: Sun, 15 Sep 2013 18:34:02 +0200 [thread overview]
Message-ID: <1379262842.9257.1.camel@dworkin> (raw)
In-Reply-To: <5235DFD2.4050008@kernel.org>
Hi,
Le dimanche 15 septembre 2013 =C3=A0 17:26 +0100, Jonathan Cameron a =C3=A9=
crit :
> On 09/06/13 11:39, Yann Droneaud wrote:
[...]
> > http://lkml.kernel.org/r/cover.1377372576.git.ydroneaud@opteya.com
> >=20
> > Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
> > Link: http://lkml.kernel.org/r/cover.1378460926.git.ydroneaud@opteya.co=
m
>=20
> Thanks Yann. I had no idea about this issue but your well supported desc=
ription
> above made this easy to review.
>=20
> Applied to the togreg branch of git://git.kernel.org/pub/scm/linux/kernel=
/git/jic23/iio.git
> as it's not a regression but if there is support for pushing this back to=
stable
> I personally am not against it.
>=20
It's not a -stable materiel. So let it flow to v3.12 or v3.13.
Thanks for the review.
Regards.
--=20
Yann Droneaud
OPTEYA
WARNING: multiple messages have this Message-ID (diff)
From: Yann Droneaud <ydroneaud@opteya.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 8/8] industrialio: use anon_inode_getfd() with O_CLOEXEC flag
Date: Sun, 15 Sep 2013 18:34:02 +0200 [thread overview]
Message-ID: <1379262842.9257.1.camel@dworkin> (raw)
In-Reply-To: <5235DFD2.4050008@kernel.org>
Hi,
Le dimanche 15 septembre 2013 à 17:26 +0100, Jonathan Cameron a écrit :
> On 09/06/13 11:39, Yann Droneaud wrote:
[...]
> > http://lkml.kernel.org/r/cover.1377372576.git.ydroneaud@opteya.com
> >
> > Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
> > Link: http://lkml.kernel.org/r/cover.1378460926.git.ydroneaud@opteya.com
>
> Thanks Yann. I had no idea about this issue but your well supported description
> above made this easy to review.
>
> Applied to the togreg branch of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> as it's not a regression but if there is support for pushing this back to stable
> I personally am not against it.
>
It's not a -stable materiel. So let it flow to v3.12 or v3.13.
Thanks for the review.
Regards.
--
Yann Droneaud
OPTEYA
next prev parent reply other threads:[~2013-09-15 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 10:39 [PATCH v3 0/8] Getting rid of get_unused_fd() / use O_CLOEXEC Yann Droneaud
2013-09-06 10:39 ` Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 1/8] ia64: use get_unused_fd_flags(0) instead of get_unused_fd() Yann Droneaud
2013-09-06 10:39 ` Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 2/8] ppc/cell: " Yann Droneaud
2013-09-06 10:39 ` Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 3/8] binfmt_misc: " Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 4/8] file: " Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 5/8] fanotify: " Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 6/8] events: " Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 7/8] file: remove get_unused_fd() Yann Droneaud
2013-09-06 10:39 ` [PATCH v3 8/8] industrialio: use anon_inode_getfd() with O_CLOEXEC flag Yann Droneaud
2013-09-15 16:26 ` Jonathan Cameron
2013-09-15 16:34 ` Yann Droneaud [this message]
2013-09-15 16:34 ` Yann Droneaud
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=1379262842.9257.1.camel@dworkin \
--to=ydroneaud@opteya.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.