Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/5] package/gutenprint: Un-deprecate and bump version to 5.2.10
Date: Sun, 24 Jan 2016 15:26:01 +0100	[thread overview]
Message-ID: <56A4DEF9.5050900@mind.be> (raw)
In-Reply-To: <CALdGskKj_MrtZCWdYHZ7XKgaHHuffV1qabrfncXpjzkBdRC=ng@mail.gmail.com>

On 24-01-16 14:50, Olivier Schonken wrote:
> Hi Thomas, All
> 
> Attached is a patch that worked for fixing the build issue you had with
> Gutenprint.  Seems they have a bit of issues with code quality control/review
> upstream.
> For the print-olympus.c file the way in which they checked the endianess
> differed from the rest of the project, and the also had a variable in genppd.c
> that was dependant on a HAVE_ZLIB define, but not encased in an #ifdef block.
> 
> If the changes are in order I will resubmit using the usual methods.
> 

 A few small comments:

 It should be two separate patches, because they do two unrelated things.

 The patch commit log for the endianness fix could be improved a little, e.g.

print-olympus.c: fix endianness detection

The __LITTLE_ENDIAN__ and __BIG_ENDIAN__ macros are not a reliable way to detect
endianness. Instead, rely on __BYTE_ORDER like we do in the rest of the code.


 There's a redundant newline in the patch description.

 And finally, don't forget to send these patches upstream.

 Thanks,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-01-24 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 22:17 [Buildroot] [PATCH v4 0/5] Buildroot Printing with Cups Olivier Schonken
2016-01-20 22:17 ` [Buildroot] [PATCH v4 1/5] package/cups: Un-deprecate, and update CUPS to 2.1.2 Olivier Schonken
2016-01-21 22:39   ` Thomas Petazzoni
2016-01-20 22:17 ` [Buildroot] [PATCH v4 2/5] package/hplip: Un-deprecate and bump version to 3.15.11 Olivier Schonken
2016-01-21 23:07   ` Thomas Petazzoni
2016-01-20 22:17 ` [Buildroot] [PATCH v4 3/5] package/gutenprint: Un-deprecate and bump version to 5.2.10 Olivier Schonken
2016-01-21 23:15   ` Thomas Petazzoni
2016-01-24 13:50     ` Olivier Schonken
2016-01-24 14:26       ` Arnout Vandecappelle [this message]
2016-01-20 22:17 ` [Buildroot] [PATCH v4 4/5] Enable xpdf-headers in poppler to enable building of cups-filters Olivier Schonken
2016-02-21 20:52   ` Thomas Petazzoni
2016-01-20 22:17 ` [Buildroot] [PATCH v4 5/5] package/cups-filters: Add new package cups-filters 1.7.0 Olivier Schonken
2016-01-24 20:06   ` Samuel Martin

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=56A4DEF9.5050900@mind.be \
    --to=arnout@mind.be \
    --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