Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libmpeg2: fix sparc32 build
Date: Thu, 27 Apr 2017 22:04:26 +0200	[thread overview]
Message-ID: <878tmlk46t.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <2a47da42-569d-129c-3a24-3154b1c335da@mind.be> (Arnout Vandecappelle's message of "Thu, 27 Apr 2017 21:30:26 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 >> Arnout, what do you think?

 >  When I spun that patch, I expected there would be more use cases than just
 > libmpeg2. But the autobuilders don't point to anything obvious, so perhaps not.

 >  I've marked as Rejected in patchwork. We can pick it up again if something else
 > turns up.

Ok, sounds sensible - Thanks!

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2017-04-27 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27  5:36 [Buildroot] [PATCH] libmpeg2: fix sparc32 build Waldemar Brodkorb
2017-04-27  8:18 ` Peter Korsgaard
2017-04-28  0:32   ` Waldemar Brodkorb
2017-04-27  8:26 ` Thomas Petazzoni
2017-04-27  9:15   ` Peter Korsgaard
2017-04-27  9:22     ` Thomas Petazzoni
2017-04-27 19:30       ` Arnout Vandecappelle
2017-04-27 20:04         ` 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=878tmlk46t.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