From: Satyam Gupta <sgsatyam@google.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Scott Collyer <scollyer@google.com>,
Benson Leung <bleung@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Satyam Gupta <sgsatyam@google.com>
Subject: Re: [PATCH v3] platform/chrome: cros_ec_sensorhub: Modify clock drift estimation
Date: Wed, 14 Oct 2026 07:42:38 +0000 [thread overview]
Message-ID: <20261014074243.2498612-1-sgsatyam@google.com> (raw)
In-Reply-To: <as8l1oKtNsIwNHWr@google.com>
Hi Tzung-Bi,
On Wed, Oct 14, 2026 at 06:48:58AM +0000, Tzung-Bi Shih wrote:
> I'm not convinced. I think they should still separate into 5 patches and
> form a series.
>
> > > On a related note, is [1] still relevant? Should we disregard it?
> > >
> > > [1] https://lore.kernel.org/all/20260720110405.2127011-1-sgsatyam@google.com
> >
> > Yes, [1] ("platform/chrome: cros_ec_sensorhub: Fix AP/EC TS wrap") is still
> > relevant — it addresses 32-bit EC timestamp rollover across deep AP suspend.
>
> Please resend or include it in the same series.
Sounds good — I have separated the changes into 5 patches, included
"platform/chrome: cros_ec_sensorhub: Fix AP/EC TS wrap" as patch 1/6, and
squashed the MAX_DRIFT_PPM = 5000LL update into patch 3/6 in the v5 series.
Best regards,
Satyam Gupta
prev parent reply other threads:[~2026-10-14 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 12:48 [PATCH] " Satyam Gupta
2026-07-23 16:36 ` [PATCH v2] framework/chrome: " Satyam Gupta
2026-07-23 16:38 ` [PATCH v3] platform/chrome: " Satyam Gupta
2026-07-28 10:15 ` Tzung-Bi Shih
2026-10-13 10:56 ` Satyam Gupta
2026-10-14 6:48 ` Tzung-Bi Shih
2026-10-14 7:42 ` 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=20261014074243.2498612-1-sgsatyam@google.com \
--to=sgsatyam@google.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scollyer@google.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®