From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linus.walleij@linaro.org, grant.likely@secretlab.ca,
horms@verge.net.au
Subject: Re: [PATCH 00/03] gpio: Renesas R-Car GPIO driver update
Date: Wed, 13 Mar 2013 12:58:37 +0000 [thread overview]
Message-ID: <1670937.hEFtzrbkf6@avalon> (raw)
In-Reply-To: <20130313113203.30133.49539.sendpatchset@w520>
Hi Magnus,
Thanks for the patches.
On Wednesday 13 March 2013 20:32:03 Magnus Damm wrote:
> gpio: Renesas R-Car GPIO driver update
>
> [PATCH 01/03] gpio: Renesas R-Car GPIO driver V2
> [PATCH 02/03] gpio: rcar: Use IRQCHIP_SET_TYPE_MASKED
> [PATCH 03/03] gpio: rcar: Make use of devm functions
>
> This series updates the R-Car GPIO driver with various
> changes kindly suggested by Laurent Pinchart.
>
> Patch [01/03] is a drop in replacement for V1 of the R-Car
> GPIO driver. The flag in patch [02/03] is kept out of [01/03]
> to avoid changing the behaviour of the driver between V1 and V2.
> Also, devm support in [03/03] is kept out of [01/03] to make
> sure back porting goes as smooth as possible.
As I mentioned in a previous e-mail, all the devm_* functions used in 03/03
have been available since 2.6.30. Do you really need to port that driver to
older kernels ?
Regarding 02/03, do you plan to squash it with 01/03 for the mainline
submission ?
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linus.walleij@linaro.org, grant.likely@secretlab.ca,
horms@verge.net.au
Subject: Re: [PATCH 00/03] gpio: Renesas R-Car GPIO driver update
Date: Wed, 13 Mar 2013 13:58:37 +0100 [thread overview]
Message-ID: <1670937.hEFtzrbkf6@avalon> (raw)
In-Reply-To: <20130313113203.30133.49539.sendpatchset@w520>
Hi Magnus,
Thanks for the patches.
On Wednesday 13 March 2013 20:32:03 Magnus Damm wrote:
> gpio: Renesas R-Car GPIO driver update
>
> [PATCH 01/03] gpio: Renesas R-Car GPIO driver V2
> [PATCH 02/03] gpio: rcar: Use IRQCHIP_SET_TYPE_MASKED
> [PATCH 03/03] gpio: rcar: Make use of devm functions
>
> This series updates the R-Car GPIO driver with various
> changes kindly suggested by Laurent Pinchart.
>
> Patch [01/03] is a drop in replacement for V1 of the R-Car
> GPIO driver. The flag in patch [02/03] is kept out of [01/03]
> to avoid changing the behaviour of the driver between V1 and V2.
> Also, devm support in [03/03] is kept out of [01/03] to make
> sure back porting goes as smooth as possible.
As I mentioned in a previous e-mail, all the devm_* functions used in 03/03
have been available since 2.6.30. Do you really need to port that driver to
older kernels ?
Regarding 02/03, do you plan to squash it with 01/03 for the mainline
submission ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-03-13 12:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 11:32 [PATCH 00/03] gpio: Renesas R-Car GPIO driver update Magnus Damm
2013-03-13 11:32 ` Magnus Damm
2013-03-13 11:32 ` [PATCH 01/03] gpio: Renesas R-Car GPIO driver V2 Magnus Damm
2013-03-13 11:32 ` Magnus Damm
2013-03-13 13:14 ` Laurent Pinchart
2013-03-13 13:14 ` Laurent Pinchart
2013-03-14 4:11 ` Magnus Damm
2013-03-14 4:11 ` Magnus Damm
2013-03-13 11:32 ` [PATCH 02/03] gpio: rcar: Use IRQCHIP_SET_TYPE_MASKED Magnus Damm
2013-03-13 11:32 ` Magnus Damm
2013-03-13 11:32 ` [PATCH 03/03] gpio: rcar: Make use of devm functions Magnus Damm
2013-03-13 11:32 ` Magnus Damm
2013-03-13 12:58 ` Laurent Pinchart [this message]
2013-03-13 12:58 ` [PATCH 00/03] gpio: Renesas R-Car GPIO driver update Laurent Pinchart
2013-03-14 4:23 ` Magnus Damm
2013-03-14 4:23 ` Magnus Damm
2013-03-14 13:13 ` Laurent Pinchart
2013-03-14 13:13 ` Laurent Pinchart
2013-03-16 8:50 ` Simon Horman
2013-03-16 8:50 ` Simon Horman
2013-03-19 3:36 ` Magnus Damm
2013-03-19 3:36 ` Magnus Damm
2013-03-19 15:01 ` Laurent Pinchart
2013-03-19 15:01 ` Laurent Pinchart
2013-03-27 12:34 ` Linus Walleij
2013-03-27 12:34 ` Linus Walleij
2013-03-27 14:44 ` Magnus Damm
2013-03-27 14:44 ` Magnus Damm
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=1670937.hEFtzrbkf6@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=grant.likely@secretlab.ca \
--cc=horms@verge.net.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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.