From: Tony Lindgren <tony@atomide.com>
To: Ilya Yanok <yanok@emcraft.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@infradead.org,
sasha_d@emcraft.com, Igor Grinberg <grinberg@compulab.co.il>
Subject: Re: [PATCH V2] OMAP2+: ads7846_init: put gpio_pendown into pdata if it's provided
Date: Mon, 5 Mar 2012 11:58:10 -0800 [thread overview]
Message-ID: <20120305195810.GR12083@atomide.com> (raw)
In-Reply-To: <1324562448-24066-1-git-send-email-yanok@emcraft.com>
* Ilya Yanok <yanok@emcraft.com> [111222 05:29]:
> If platform data is provided by the caller gpio_pendown is put into
> unused static ads7846_config structure and effectively has no effect.
> Of course caller can set gpio_pendown field in platform data himself
> but it seems natural to do this in ads7846_init to remove duplication.
Thanks applying into fixes-non-critical-part2.
Regards,
Tony
prev parent reply other threads:[~2012-03-05 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 14:00 [PATCH V2] OMAP2+: ads7846_init: put gpio_pendown into pdata if it's provided Ilya Yanok
2012-03-05 19:58 ` Tony Lindgren [this message]
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=20120305195810.GR12083@atomide.com \
--to=tony@atomide.com \
--cc=grinberg@compulab.co.il \
--cc=linux-arm-kernel@infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.com \
--cc=yanok@emcraft.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 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).