From: Pratyush Yadav <pratyush@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Jakub Czapiga <czapiga@google.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Michael Walle <mwalle@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Konrad Adamczyk <konrada@google.com>,
Adeel Arshad <adeel.arshad@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Kornel Duleba <korneld@google.com>
Subject: Re: [PATCH v2] mtd: spi-nor: core: Check read CR support
Date: Thu, 20 Nov 2025 10:27:02 +0100 [thread overview]
Message-ID: <mafs0ecpt2gwp.fsf@kernel.org> (raw)
In-Reply-To: <20251118-stereotyped-quizzical-dolphin-9a7bb4@lemur> (Konstantin Ryabitsev's message of "Tue, 18 Nov 2025 09:20:48 -0500")
On Tue, Nov 18 2025, Konstantin Ryabitsev wrote:
> On Tue, Nov 18, 2025 at 01:34:59PM +0100, Pratyush Yadav wrote:
>> BTW, b4 complains that DKIM fails on your email. Please check.
>
> This is due to Google's policy of setting very short expiration dates in their
> DKIM headers:
>
> t=1758305794; x=1758910594;
>
> It's set to invalidate after 1 week:
>
> $ date -d '@1758305794'
> Fri 19 Sep 2025 02:16:34 PM EDT
> $ date -d '@1758910594'
> Fri 26 Sep 2025 02:16:34 PM EDT
I see. Thanks for explaining!
--
Regards,
Pratyush Yadav
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2025-11-20 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:15 [PATCH v2] mtd: spi-nor: core: Check read CR support Jakub Czapiga
2025-11-18 12:34 ` Pratyush Yadav
2025-11-18 14:20 ` Konstantin Ryabitsev
2025-11-20 9:27 ` Pratyush Yadav [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=mafs0ecpt2gwp.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=adeel.arshad@intel.com \
--cc=czapiga@google.com \
--cc=konrada@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=korneld@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mika.westerberg@linux.intel.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).