From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] transmission: Fix build error "conflicting types for 'UTP_Write'" after version bump
Date: Fri, 3 Jan 2014 20:42:25 +0100 [thread overview]
Message-ID: <20140103204225.0e1998be@skate> (raw)
In-Reply-To: <BLU0-SMTP19793343AE004AB8BB60FDFD9CA0@phx.gbl>
Dear Bernd Kuhls,
On Fri, 3 Jan 2014 20:18:21 +0100, Bernd Kuhls wrote:
> fix taken from
> http://www.adminsehow.com/2012/10/how-to-install-transmission-2-71-on-debian-6-0-squeeze/
>
> compile tested on arch sh4, fixes
> http://autobuild.buildroot.org/results/638/63884de929fb7339ebf44b08cb5d1ab30010666a/
>
> should also fix powerpc
> http://autobuild.buildroot.org/results/eb4/eb486228a11a9602d4bf40e771744d2b2b40508f/
>
> Signed-off-by: Bernd Kuhls <berndkuhls@hotmail.com>
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-03 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 19:18 [Buildroot] [PATCH v2 1/1] transmission: Fix build error "conflicting types for 'UTP_Write'" after version bump Bernd Kuhls
2014-01-03 19:42 ` Thomas Petazzoni [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=20140103204225.0e1998be@skate \
--to=thomas.petazzoni@free-electrons.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