mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr, tools@kernel.org
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Distributed data processing for SmPL scripts
Date: Mon, 2 Nov 2026 10:34:02 +0100	[thread overview]
Message-ID: <7a14fdbc-fefe-4c7e-8b57-3c42b5d1a453@web.de> (raw)
In-Reply-To: <b55ad049-86e0-f737-a96a-f3151db5012@inria.fr>

>> Some developers got used to tools which support distributed data processing
>> for compilation tasks.
>>
>> Examples:
>> https://www.distcc.org/
>> https://github.com/icecc/icecream
> 
> Maybe such things can just be used off the shelf, since Coccinelle can be
> invoked from make.

Did you notice how such development tools were implemented?

How would you distinguish single programs from a service-oriented architecture?


> In any case, I have no intention of working on this.

Under which circumstances would you become more interested in related topics?

How many components can eventually be extracted from the OCaml (and Rust)
implementation for better reuse with other programming languages?


>                                                       If you want to
> contribute something, please go ahead.

I would appreciate additional development resources also for advanced
source code analyses and transformations.

Regards,
Markus

      reply	other threads:[~2026-11-02  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-01 12:37 Markus Elfring
2026-11-01 15:05 ` Julia Lawall
2026-11-02  9:34   ` Markus Elfring [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=7a14fdbc-fefe-4c7e-8b57-3c42b5d1a453@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tools@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®