From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>, <wsa@the-dreams.de>
Cc: <thierry.reding@gmail.com>, <andrewc@nvidia.com>,
<gnurou@gmail.com>, <linux-i2c@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Chaitanya Bandi <bandik@nvidia.com>
Subject: Re: [RFT PATCH 1/2] i2c: tegra: update CONFIG_LOAD for new conifiguration
Date: Thu, 9 Jul 2015 11:10:24 +0530 [thread overview]
Message-ID: <559E0948.1050004@nvidia.com> (raw)
In-Reply-To: <559D89D8.50500@wwwdotorg.org>
On Thursday 09 July 2015 02:06 AM, Stephen Warren wrote:
> On 06/30/2015 04:54 AM, Laxman Dewangan wrote:
>>
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>> Signed-off-by: Chaitanya Bandi <bandik@nvidia.com>
>
> I'm not sure why Chaitanya's S-o-b is there and listed last if he's
> not the patch author. If he wrote the patch, he should be the git
> author and his S-o-b should be first. If he didn't and you simply
> based this patch on work by Chaitanya, then his S-o-b probably
> shouldn't be present, and yours would be last since you're submitting
> the patch.
The patch I created is based on Chaitanya's work, edited on his work to
match with mainline.
>
>> ---
>> Stephen/Andrew,
>> I need help on testing this on other platform. I tested this on T210.
>
> I'm puzzled how this was tested on T210, since it isn't supported
> upstream yet.
We tested this as:
- K318 kernel release + i2c subsystem from linux-next in downstream boards.
- Chrome-OS team on smaug with their tree.
> The series,
> Tested-by: Stephen Warren <swarren@nvidia.com>
Thanks for testing.
next prev parent reply other threads:[~2015-07-09 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 10:54 Laxman Dewangan
2015-06-30 10:54 ` [RFT PATCH 2/2] i2c: tegra: add support for fast plus (FM+) mode clock rate Laxman Dewangan
2015-07-31 10:43 ` Wolfram Sang
2015-07-08 20:36 ` [RFT PATCH 1/2] i2c: tegra: update CONFIG_LOAD for new conifiguration Stephen Warren
2015-07-09 5:40 ` Laxman Dewangan [this message]
2015-07-16 10:16 ` Laxman Dewangan
2015-07-31 10:42 ` 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=559E0948.1050004@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=andrewc@nvidia.com \
--cc=bandik@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/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
Powered by JetHome