From: Markus Elfring <Markus.Elfring@web.de>
To: Easwar Hariharan <eahariha@linux.microsoft.com>,
cocci@inria.fr, Andrew Morton <akpm@linux-foundation.org>,
Dongsheng Yang <dongsheng.yang@easystack.cn>,
Ilya Dryomov <idryomov@gmail.com>, Jens Axboe <axboe@kernel.dk>,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Ricardo Ribalda <ribalda@chromium.org>,
Xiubo Li <xiubli@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [cocci] [PATCH v2 1/3] coccinelle: misc: secs_to_jiffies: Patch expressions too
Date: Tue, 4 Feb 2025 08:56:06 +0100 [thread overview]
Message-ID: <49533960-e437-4042-951a-0221164bfa3d@web.de> (raw)
In-Reply-To: <20250203-converge-secs-to-jiffies-part-two-v2-1-d7058a01fd0e@linux.microsoft.com>
> Teach the script to suggest conversions for timeout patterns where the
> arguments to msecs_to_jiffies() are expressions as well.
How do you imagine that the shown SmPL code fits ever to patch reviews?
Examples:
* https://lore.kernel.org/cocci/80cae791-663c-4589-b67e-d4d1049fcd98@web.de/
https://sympa.inria.fr/sympa/arc/cocci/2025-02/msg00002.html
https://lkml.org/lkml/2025/2/3/151
* https://lore.kernel.org/cocci/e06cb7f5-7aa3-464c-a8a1-2c7b9b6a29eb@web.de/
https://sympa.inria.fr/sympa/arc/cocci/2025-01/msg00122.html
https://lkml.org/lkml/2025/1/30/307
Regards,
Markus
next prev parent reply other threads:[~2025-02-04 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 23:50 [PATCH v2 0/3] Converge on using secs_to_jiffies() part two Easwar Hariharan
2025-02-03 23:50 ` [PATCH v2 1/3] coccinelle: misc: secs_to_jiffies: Patch expressions too Easwar Hariharan
2025-02-04 7:56 ` Markus Elfring [this message]
2025-02-04 16:20 ` [cocci] " Easwar Hariharan
2025-02-04 20:24 ` [cocci] [v2 " Markus Elfring
2025-02-03 23:50 ` [PATCH v2 2/3] rbd: convert timeouts to secs_to_jiffies() Easwar Hariharan
2025-02-04 20:15 ` Ilya Dryomov
2025-02-03 23:50 ` [PATCH v2 3/3] libceph: " Easwar Hariharan
2025-02-04 20:16 ` Ilya Dryomov
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=49533960-e437-4042-951a-0221164bfa3d@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=cocci@inria.fr \
--cc=dongsheng.yang@easystack.cn \
--cc=eahariha@linux.microsoft.com \
--cc=idryomov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=ribalda@chromium.org \
--cc=xiubli@redhat.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