Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8] Fix the Config.in prefix of a number of options
Date: Mon, 21 May 2018 23:18:07 +0200	[thread overview]
Message-ID: <87sh6kiu7k.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180513190737.26079-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Sun, 13 May 2018 21:07:29 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > This series was started from Petr Vorel's patch fixing libmediaart
 > options, which had a wrong prefix. I started writing an additional
 > check in check-package for this mistake, and thanks to it, I
 > discovered a number of other issues, fixed by this patch series.

 > Best regards,

 > Thomas

 > Petr Vorel (1):
 >   libmediaart: rename options to have proper prefix

 > Thomas Petazzoni (7):
 >   bluez5_utils: rename options to have the proper suffix
 >   jquery-ui-themes: rename options to have proper prefix
 >   libftdi: rename option to have proper prefix
 >   ipsec-tools: rename options to have proper prefix
 >   janus-gateway: rename options to have proper prefix
 >   ti-sgx-km: rename options to have proper prefix

Committed all of these, thanks. The improvements to Config.in.legacy can
be handled as a followup series.

>   utils/check-package: verify the prefix of package Config.in options

But not this one as there was quite some feedback on this.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-05-21 21:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 19:07 [Buildroot] [PATCH 0/8] Fix the Config.in prefix of a number of options Thomas Petazzoni
2018-05-13 19:07 ` [Buildroot] [PATCH 1/8] bluez5_utils: rename options to have the proper suffix Thomas Petazzoni
2018-05-13 19:18   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 2/8] jquery-ui-themes: rename options to have proper prefix Thomas Petazzoni
2018-05-13 19:19   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 3/8] libftdi: rename option " Thomas Petazzoni
2018-05-13 19:19   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 4/8] ipsec-tools: rename options " Thomas Petazzoni
2018-05-13 19:21   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 5/8] janus-gateway: " Thomas Petazzoni
2018-05-13 19:22   ` Yann E. MORIN
2018-05-14  4:00   ` Ricardo Martincoski
2018-05-13 19:07 ` [Buildroot] [PATCH 6/8] ti-sgx-km: " Thomas Petazzoni
2018-05-13 19:31   ` Yann E. MORIN
2018-05-15 21:52     ` Arnout Vandecappelle
2018-05-16  7:00       ` Thomas Petazzoni
2018-05-16 15:16         ` Arnout Vandecappelle
2018-05-21 21:16           ` Peter Korsgaard
2018-05-22 10:42             ` Arnout Vandecappelle
2018-05-28 20:45               ` Yann E. MORIN
2018-05-29 10:45                 ` Arnout Vandecappelle
2018-05-29 17:26                   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 7/8] libmediaart: " Thomas Petazzoni
2018-05-13 19:32   ` Yann E. MORIN
2018-05-13 19:07 ` [Buildroot] [PATCH 8/8] utils/check-package: verify the prefix of package Config.in options Thomas Petazzoni
2018-05-14  4:04   ` Ricardo Martincoski
2018-05-21 21:18 ` Peter Korsgaard [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=87sh6kiu7k.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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