From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Bitan Biswas <bbiswas@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shardar Mohammed <smohammed@nvidia.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Mantravadi Karthik <mkarthik@nvidia.com>
Subject: Re: [PATCH V3] i2c: busses: tegra: Add suspend-resume support
Date: Mon, 17 Jun 2019 09:02:59 +0200 [thread overview]
Message-ID: <20190617070259.GA30126@ulmo> (raw)
In-Reply-To: <69a9a7e3-f885-b6ab-60bb-a1165ce2db23@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Sun, Jun 16, 2019 at 04:56:06PM +0300, Dmitry Osipenko wrote:
> 15.06.2019 7:54, Wolfram Sang пишет:
> >
> >>> Without a maintainer ack, this is an exception this time. Should we add
> >>> Dmitry as another maintainer or reviewer at least?
> >>>
> >> I shall followup with Maintainer for ACK in future I2C tegra patches.
> >
> > This comment was not directed at you, sorry if that was not clear. It
> > was more for Laxman, Thierry, Jonathan, and Dmitry (if he is
> > interested).
> >
>
> I don't mind at all to review and test patches for the driver and can propose myself
> as a reviewer if that helps and if there are no objections from the Tegra maintainers.
> My primary interest is to have my devices working after next kernel update, but I also
> like to review patches in general if they are touching area that I'm familiar with.
No objection from me.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-17 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 5:37 [PATCH V3] i2c: busses: tegra: Add suspend-resume support Bitan Biswas
2019-06-07 5:37 ` Bitan Biswas
2019-06-07 6:27 ` Dmitry Osipenko
2019-06-13 12:00 ` Bitan Biswas
2019-06-13 12:00 ` Bitan Biswas
2019-06-14 21:11 ` Wolfram Sang
2019-06-15 4:36 ` Bitan Biswas
2019-06-15 4:36 ` Bitan Biswas
2019-06-15 4:54 ` Wolfram Sang
2019-06-16 13:56 ` Dmitry Osipenko
2019-06-17 7:02 ` Thierry Reding [this message]
2019-06-17 12:16 ` Dmitry Osipenko
2019-06-17 7:09 ` Thierry Reding
2019-06-17 17:58 ` Bitan Biswas
2019-06-17 17:58 ` Bitan Biswas
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=20190617070259.GA30126@ulmo \
--to=thierry.reding@gmail.com \
--cc=bbiswas@nvidia.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkarthik@nvidia.com \
--cc=skomatineni@nvidia.com \
--cc=smohammed@nvidia.com \
--cc=treding@nvidia.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 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.