Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mesa3d: drop unneeded libsha1 logic from Config.in
Date: Tue, 28 Mar 2017 21:49:40 +0200	[thread overview]
Message-ID: <46864719-9b77-2140-d5bb-937cebdbb0ff@gmail.com> (raw)
In-Reply-To: <20170328214404.1003ccbb@free-electrons.com>

Hi Peter, All,

Le 28/03/2017 ? 21:44, Thomas Petazzoni a ?crit :
> Hello,
> 
> On Tue, 28 Mar 2017 14:30:21 +0200, Peter Korsgaard wrote:
>> Commit 7f4e9490b647 (package/mesa3d: remove sha1 external dependency)
>> removed the --with-sha1 logic from mesa3d.mk, but didn't remove the
>> corresponding logic / comment from Config.in.
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
>> ---
>>  package/mesa3d/Config.in | 4 ----
>>  1 file changed, 4 deletions(-)
> 
> Applied to master, thanks. Good catch!

Back on line too late to ack this patch :p

Thanks!

Romain

> 
> Thomas
> 

      reply	other threads:[~2017-03-28 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 12:30 [Buildroot] [PATCH] mesa3d: drop unneeded libsha1 logic from Config.in Peter Korsgaard
2017-03-28 19:44 ` Thomas Petazzoni
2017-03-28 19:49   ` Romain Naour [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=46864719-9b77-2140-d5bb-937cebdbb0ff@gmail.com \
    --to=romain.naour@gmail.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