From: Wolfram Sang <wsa@the-dreams.de>
To: Shardar Shariff Md <smohammed@nvidia.com>
Cc: swarren@wwwdotorg.org, thierry.reding@gmail.com,
gnurou@gmail.com, linux-i2c@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
jonathanh@nvidia.com
Subject: Re: [PATCH v10 2/4] i2c: tegra: add separate function for config_load programing
Date: Tue, 30 Aug 2016 22:30:03 +0200 [thread overview]
Message-ID: <20160830203003.GA3645@katana> (raw)
In-Reply-To: <1472584279-19924-2-git-send-email-smohammed@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
On Wed, Aug 31, 2016 at 12:41:17AM +0530, Shardar Shariff Md wrote:
> Define separate function for configuration load register handling
> to make it use by different functions later.
>
> Signed-off-by: Shardar Shariff Md <smohammed@nvidia.com>
SMATCH
drivers/i2c/busses/i2c-tegra.c:519 tegra_i2c_init warn: unused return: err = tegra_i2c_flush_fifos()
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-30 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 19:11 [PATCH v10 1/4] i2c: tegra: use readl_poll_timeout after config_load reg programmed Shardar Shariff Md
2016-08-30 19:11 ` [PATCH v10 2/4] i2c: tegra: add separate function for config_load programing Shardar Shariff Md
2016-08-30 20:30 ` Wolfram Sang [this message]
2016-08-30 19:11 ` [PATCH v10 3/4] i2c: tegra: use atomic poll function during configuration Shardar Shariff Md
[not found] ` <1472584279-19924-3-git-send-email-smohammed-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-08-30 20:30 ` Wolfram Sang
2016-08-30 19:11 ` [PATCH v10 4/4] i2c: tegra: proper handling of error cases Shardar Shariff Md
[not found] ` <1472584279-19924-1-git-send-email-smohammed-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-08-30 20:32 ` [PATCH v10 1/4] i2c: tegra: use readl_poll_timeout after config_load reg programmed Wolfram Sang
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=20160830203003.GA3645@katana \
--to=wsa@the-dreams.de \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smohammed@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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 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).