From: Christoph Hellwig <hch@lst.de>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/16] Converge on using secs_to_jiffies() part two
Date: Wed, 26 Feb 2025 02:11:42 +0100 [thread overview]
Message-ID: <20250226011142.GA27339@lst.de> (raw)
In-Reply-To: <20250225-converge-secs-to-jiffies-part-two-v3-0-a43967e36c88@linux.microsoft.com>
On Tue, Feb 25, 2025 at 08:17:14PM +0000, Easwar Hariharan wrote:
> This is the second series (part 1*) that converts users of msecs_to_jiffies() that
It's not a series. It's a set of not interdependent cross-subsystem
patches that you post as a series, thus causing tons of traffic for
no reason, and requires me to manually approve mailing list posts
every time, including for each reply.
Please just send the patches you need to resend individually next time.
next prev parent reply other threads:[~2025-02-26 1:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 20:17 [PATCH v3 00/16] Converge on using secs_to_jiffies() part two Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 01/16] coccinelle: misc: secs_to_jiffies: Patch expressions too Easwar Hariharan
2025-02-26 8:26 ` [cocci] " Markus Elfring
2025-02-25 20:17 ` [PATCH v3 02/16] scsi: lpfc: convert timeouts to secs_to_jiffies() Easwar Hariharan
2025-03-04 2:11 ` Martin K. Petersen
2025-02-25 20:17 ` [PATCH v3 03/16] accel/habanalabs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 04/16] ALSA: ac97: " Easwar Hariharan
2025-02-26 11:55 ` [cocci] " Markus Elfring
2025-02-25 20:17 ` [PATCH v3 05/16] btrfs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 06/16] rbd: " Easwar Hariharan
2025-02-25 21:09 ` Christophe JAILLET
2025-02-26 0:02 ` Easwar Hariharan
2025-02-26 7:28 ` Daniel Vacek
2025-02-26 8:10 ` Christophe JAILLET
2025-02-26 8:29 ` Daniel Vacek
2025-02-25 20:17 ` [PATCH v3 07/16] libceph: " Easwar Hariharan
2025-02-25 21:25 ` Christophe JAILLET
2025-02-25 20:17 ` [PATCH v3 08/16] ata: libata-zpodd: " Easwar Hariharan
2025-02-25 20:24 ` Easwar Hariharan
2025-02-26 2:00 ` Damien Le Moal
2025-02-25 20:17 ` [PATCH v3 09/16] xfs: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 10/16] power: supply: da9030: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 11/16] nvme: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 12/16] spi: spi-fsl-lpspi: " Easwar Hariharan
2025-02-25 20:17 ` [PATCH v3 13/16] spi: spi-imx: " Easwar Hariharan
2025-02-25 20:27 ` Marc Kleine-Budde
2025-02-25 20:17 ` [PATCH v3 14/16] platform/x86/amd/pmf: " Easwar Hariharan
2025-03-21 16:08 ` Ilpo Järvinen
2025-02-25 20:17 ` [PATCH v3 15/16] platform/x86: thinkpad_acpi: " Easwar Hariharan
2025-03-21 16:06 ` Ilpo Järvinen
2025-02-25 20:17 ` [PATCH v3 16/16] RDMA/bnxt_re: " Easwar Hariharan
2025-02-25 20:30 ` (subset) [PATCH v3 00/16] Converge on using secs_to_jiffies() part two Jens Axboe
2025-02-26 1:11 ` Christoph Hellwig [this message]
2025-02-26 11:29 ` Mark Brown
2025-02-26 20:38 ` Andrew Morton
2025-02-26 22:26 ` Mark Brown
2025-02-27 9:02 ` Carlos Maiolino
2025-02-26 16:48 ` (subset) " Mark Brown
2025-03-11 1:19 ` Martin K. Petersen
2025-03-11 2:08 ` Andrew Morton
2025-03-11 2:29 ` Martin K. Petersen
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=20250226011142.GA27339@lst.de \
--to=hch@lst.de \
--cc=eahariha@linux.microsoft.com \
--cc=linux-kernel@vger.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