From: Kent Gibson <warthog618@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Andrew Jeffery" <andrew@aj.id.au>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>
Subject: Re: [libgpiod][WIP PATCH 0/2] Convert the build from autotools to meson
Date: Tue, 6 Dec 2022 11:54:58 +0800 [thread overview]
Message-ID: <Y469EqS544Klls+5@sol> (raw)
In-Reply-To: <20221206034034.wranm36qjdd5ueqp@vireshk-i7>
On Tue, Dec 06, 2022 at 09:10:34AM +0530, Viresh Kumar wrote:
> On 06-12-22, 10:56, Andrew Jeffery wrote:
> > My experience with rust is (unfortunately) superficial; the meson
> > conversion achieves the same outcome as the autotools integration (runs
> > `cargo build ...`). If that's enough then I don't think there are any
> > further issues.
>
> That's all I care about at the moment. Lets see if Kent have something
> to add to this, else it looks okay.
>
I've got nothing to add - calling cargo makes sense to me.
Cheers,
Kent.
next prev parent reply other threads:[~2022-12-06 3:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 13:22 [libgpiod][WIP PATCH 0/2] Convert the build from autotools to meson Andrew Jeffery
2022-12-05 13:22 ` [libgpiod][WIP PATCH 1/2] Introduce meson as a build system Andrew Jeffery
2022-12-05 13:22 ` [libgpiod][WIP PATCH 2/2] Remove autotools in favour of meson Andrew Jeffery
2022-12-05 18:55 ` [libgpiod][WIP PATCH 0/2] Convert the build from autotools to meson Bartosz Golaszewski
2022-12-05 23:42 ` Andrew Jeffery
2022-12-06 0:06 ` Viresh Kumar
2022-12-06 0:26 ` Andrew Jeffery
2022-12-06 3:40 ` Viresh Kumar
2022-12-06 3:54 ` Kent Gibson [this message]
2022-12-06 12:15 ` Miguel Ojeda
2022-12-06 14:54 ` Andy Shevchenko
2022-12-06 22:04 ` Andrew Jeffery
2022-12-06 22:21 ` Andy Shevchenko
2022-12-08 4:23 ` Andrew Jeffery
2022-12-08 9:27 ` Bartosz Golaszewski
2022-12-08 11:09 ` Andrew Jeffery
2022-12-08 18:48 ` Bartosz Golaszewski
2022-12-08 21:51 ` Andrew Jeffery
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=Y469EqS544Klls+5@sol \
--to=warthog618@gmail.com \
--cc=andrew@aj.id.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn3_gh@protonmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).