mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satyam Gupta <sgsatyam@google.com>
To: Joshua Crofts <crofts@kernel.org>
Cc: "Satyam Gupta" <sgsatyam@google.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Benson Leung" <bleung@chromium.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Tzung-Bi Shih" <tzungbi@kernel.org>,
	"Enric Balletbo i Serra" <eballetbo@kernel.org>,
	linux-iio@vger.kernel.org, chrome-platform@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] iio: cros_ec: Use platform sensor_num to unregister FIFO callback
Date: Fri,  6 Nov 2026 17:41:47 +0000	[thread overview]
Message-ID: <20261106174147.1351648-1-sgsatyam@google.com> (raw)
In-Reply-To: <20261106102217.3bd67592@systembl0wer>

On Fri, 6 Nov 2026 10:22:17 +0100, Joshua Crofts wrote:
> No, don't send a new version of a patch as a reply to the
> previous version, it may break tooling like b4 for example.

Got it, thanks for pointing that out. I will make sure future revisions
start a new thread instead of using --in-reply-to.

Thanks,
Satyam

      reply	other threads:[~2026-11-06 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  7:31 [PATCH] " Satyam Gupta
2026-11-05 10:00 ` Andy Shevchenko
2026-11-05 13:20 ` [PATCH v2] " Satyam Gupta
2026-11-06  3:10   ` Tzung-Bi Shih
2026-11-06  7:19     ` [PATCH v3] " Satyam Gupta
2026-11-06  9:22       ` Joshua Crofts
2026-11-06 17:41         ` Satyam Gupta [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=20261106174147.1351648-1-sgsatyam@google.com \
    --to=sgsatyam@google.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=crofts@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eballetbo@kernel.org \
    --cc=groeck@chromium.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=tzungbi@kernel.org \
    /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®