All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Zoltan Gyarmati <zgyarmati@zgyarmati.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libusb-compat: bump to 0.1.8
Date: Sat, 12 Aug 2023 21:55:59 +0200	[thread overview]
Message-ID: <20230812215559.65936b40@windsurf> (raw)
In-Reply-To: <20230812175348.1449808-1-zgyarmati@zgyarmati.de>

On Sat, 12 Aug 2023 19:53:48 +0200
Zoltan Gyarmati <zgyarmati@zgyarmati.de> wrote:

> Removing upstreamed patch and force autoreconf

Thanks for your patch. However, why is the force autoreconf needed? We
need to have a comment above this line in the .mk file that explains
why.

Thanks a lot!

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

  reply	other threads:[~2023-08-12 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 17:53 [Buildroot] [PATCH 1/1] package/libusb-compat: bump to 0.1.8 Zoltan Gyarmati
2023-08-12 19:55 ` Thomas Petazzoni via buildroot [this message]
2023-08-12 21:54   ` Zoltan Gyarmati
2023-08-12 22:08     ` Thomas Petazzoni 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=20230812215559.65936b40@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=zgyarmati@zgyarmati.de \
    /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.