Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Saurav Sachidanand <sauravsc@amazon.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	 Akhil R <akhilrajeev@nvidia.com>,
	Kartik Rajput <kkartik@nvidia.com>,
	 Thierry Reding <treding@nvidia.com>,
	Jon Hunter <jonathanh@nvidia.com>,
	linux-i2c@vger.kernel.org,  linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] i2c: tegra: fix error handling in tegra_i2c_xfer()
Date: Thu, 14 May 2026 00:24:01 +0200	[thread overview]
Message-ID: <agT5mMELzPZRBTQv@zenone.zhora.eu> (raw)
In-Reply-To: <20260507221145.62183-1-sauravsc@amazon.com>

Hi Saurav,

> Saurav Sachidanand (2):
>   i2c: tegra: fix pm_runtime leak on mutex_lock failure
>   i2c: tegra: make tegra_i2c_mutex_unlock() return void

merged to i2c/i2c-host-fixes.

Next time, please:

 - don't forget to add me in Cc
 - to not nest in the same thread different versions. It would
   have been clearer if v2 was in its own thread.

Thanks,
Andi

      parent reply	other threads:[~2026-05-13 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 19:53 [PATCH 1/1] i2c: tegra: fix error handling in tegra_i2c_xfer() Saurav Sachidanand
2026-05-07  7:23 ` Jon Hunter
2026-05-07 22:11 ` [PATCH v2 0/2] " Saurav Sachidanand
2026-05-07 22:11   ` [PATCH v2 1/2] i2c: tegra: fix pm_runtime leak on mutex_lock failure Saurav Sachidanand
2026-05-08 10:24     ` Thierry Reding
2026-05-08 15:13       ` Jon Hunter
2026-05-07 22:11   ` [PATCH v2 2/2] i2c: tegra: make tegra_i2c_mutex_unlock() return void Saurav Sachidanand
2026-05-08 10:24     ` Thierry Reding
2026-05-08 15:14       ` Jon Hunter
2026-05-13 22:24   ` Andi Shyti [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=agT5mMELzPZRBTQv@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=akhilrajeev@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=kkartik@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=sauravsc@amazon.com \
    --cc=treding@nvidia.com \
    --cc=wsa+renesas@sang-engineering.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