mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Rosin <peda@axentia.se>
To: Sowjanya Komatineni <skomatineni@nvidia.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Timo Alho <talho@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH V1] i2c: tegra: Fix Maximum transfer size
Date: Wed, 2 Jan 2019 23:02:10 +0000	[thread overview]
Message-ID: <20cf9eb0-d8f6-7a85-3fb7-2c3aa5e41f31@axentia.se> (raw)
In-Reply-To: <BN7PR12MB283656FC1AA704474BC52728C28C0@BN7PR12MB2836.namprd12.prod.outlook.com>

On 2019-01-02 23:39, Sowjanya Komatineni wrote:
>>> +static const struct i2c_adapter_quirks tegra194_i2c_quirks = {
>>> +	.flags = I2C_AQ_NO_ZERO_LEN,
>>
>> This is not mentioned in the commit message and the flag is not present in the old struct tegra_i2c_quirks above. Are you trying to sneak changes past the maintainers, or was the change simply not intentional?
> Flag of NO_ZERO_LEN is present in tegra_i2c_quirks as well. I have added separate quirk with same flag and payload change for Tegra194

*blush*

I was comparing with old sources. Sorry!

Cheers,
Peter

  reply	other threads:[~2019-01-02 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 21:48 Sowjanya Komatineni
2019-01-02 22:05 ` Peter Rosin
2019-01-02 22:39   ` Sowjanya Komatineni
2019-01-02 23:02     ` Peter Rosin [this message]
2019-01-03  4:47 ` kbuild test robot

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=20cf9eb0-d8f6-7a85-3fb7-2c3aa5e41f31@axentia.se \
    --to=peda@axentia.se \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=skomatineni@nvidia.com \
    --cc=talho@nvidia.com \
    --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

all inboxes | Powered by JetHome®