public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Lukasz Gut <lgut@lgut.eu>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: sbrivio@redhat.com, sevinj.aghayeva@gmail.com, passt-dev@passt.top
Subject: Re: [PATCH v2 0/4] mbuto: Make it work on Arch Linux
Date: Mon, 23 Sep 2024 12:09:07 +0200	[thread overview]
Message-ID: <e5edc00dae82383fbd113f211c51e0fe39a8b7e2.camel@lgut.eu> (raw)
In-Reply-To: <ZvDkdj7m0-3kM4re@zatzit.fritz.box>

On Mon, 2024-09-23 at 13:45 +1000, David Gibson wrote:
> On Wed, Sep 18, 2024 at 12:12:54PM +0200, Lukasz Gut wrote:
> > Hi Stefano,
> > 
> > This set of patches makes mbuto work also on Arch Linux.
> > I have changed PATCH 4/4 based on your comments.
> > 
> > Thank you for pointing out the correct recepient list.
> 
> One overall nit in the commit messages, rather than the patches themslves:
> 
> To me "ld" without clarification means the static linker not the
> dynamic linker (that's "ld.so").  But many of your messages are
> referring to the dynamic linker as "ld".

Thanks David for pointing that out, I will be more specific next time.


--
Lukasz

      reply	other threads:[~2024-09-23 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 10:12 [PATCH v2 0/4] mbuto: Make it work on Arch Linux Lukasz Gut
2024-09-18 10:12 ` [PATCH v2 1/4] mbuto: Pick a src when ld reported as link by ldd Lukasz Gut
2024-09-23  3:51   ` David Gibson
2024-09-23 10:09     ` Lukasz Gut
2024-09-18 10:12 ` [PATCH v2 2/4] mbuto: Use realpath to copy ld Lukasz Gut
2024-09-23  3:53   ` David Gibson
2024-09-23 10:09     ` Lukasz Gut
2024-09-18 10:12 ` [PATCH v2 3/4] mbuto: Don't try to add ld when adding libraries Lukasz Gut
2024-09-18 10:12 ` [PATCH v2 4/4] mbuto: Automatically add links related to linker Lukasz Gut
2024-09-23  3:54   ` David Gibson
2024-09-23 10:09     ` Lukasz Gut
2024-09-23  3:45 ` [PATCH v2 0/4] mbuto: Make it work on Arch Linux David Gibson
2024-09-23 10:09   ` Lukasz Gut [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=e5edc00dae82383fbd113f211c51e0fe39a8b7e2.camel@lgut.eu \
    --to=lgut@lgut.eu \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    --cc=sevinj.aghayeva@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).