From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sebastian WEYER <sebastian.weyer@smile.fr>
Cc: Romain Naour <romain.naour@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/rust-bindgen: new host package
Date: Tue, 4 Jul 2023 15:33:45 +0200 [thread overview]
Message-ID: <20230704153345.153f73ac@windsurf> (raw)
In-Reply-To: <CADSVbUsPFy5-CZ22BUU_dYAGc-=ycpJYAKSmdj7nYm96Nn5PBQ@mail.gmail.com>
Hello Sebastian,
On Tue, 4 Jul 2023 12:50:16 +0200
Sebastian WEYER <sebastian.weyer@smile.fr> wrote:
> Thank you for your feedback.
> It was an oversight to leave the comment as is, as initially the package
> was added with a version <0.63.0.
> Do you think a comment explaining the command line options being deprecated
> should stay? Also considering that the Kernel still uses these options for
> its Rust modules.
Ah, so the proposed version of rust-bindgen would not work to support
the in-kernel Rust support? This is a bit unfortunate.
Regarding the comment, I'm not sure they make sense. If we start
documenting all what's no longer supported by a given package,
Buildroot would be full of comments related to obsolete features :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-04 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:50 [Buildroot] [PATCH 1/1] package/rust-bindgen: new host package Sebastian Weyer
2023-07-03 20:41 ` Thomas Petazzoni via buildroot
2023-07-04 10:50 ` Sebastian WEYER
2023-07-04 13:33 ` Thomas Petazzoni via buildroot [this message]
2023-07-04 14:24 ` Sebastian WEYER
2023-07-04 20:30 ` Sebastian WEYER
2023-07-04 20:36 ` Arnout Vandecappelle via buildroot
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=20230704153345.153f73ac@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=sebastian.weyer@smile.fr \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.