From: chrubis@suse.cz
To: Markos Chandras <Markos.Chandras@imgtec.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] utils: sctp: Fix build for prefixed architectures
Date: Mon, 13 Jan 2014 19:54:06 +0100 [thread overview]
Message-ID: <20140113185405.GA2315@rei> (raw)
In-Reply-To: <52CFC57F.9000004@imgtec.com>
Hi!
> I am also able to build the upstream code directly from their repository.
>
> Could you please double check the patch you applied? :)
And indeed it was misapplied, for same strange reason the 'git am' dropped
last two lines of the patch. Which keeps me wonder how many patches has
been corrupted silently :(
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-01-13 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 12:31 [LTP] [PATCH v2] utils: sctp: Fix build for prefixed architectures Markos Chandras
2013-12-16 6:58 ` Mike Frysinger
2013-12-20 12:45 ` Markos Chandras
2014-01-05 22:30 ` Mike Frysinger
2014-01-08 13:30 ` chrubis
[not found] ` <201401081644.28915.vapier@gentoo.org>
2014-01-09 11:57 ` chrubis
2014-01-09 11:53 ` chrubis
[not found] ` <52CE9B15.4070307@imgtec.com>
[not found] ` <52CFC57F.9000004@imgtec.com>
2014-01-13 18:54 ` chrubis [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=20140113185405.GA2315@rei \
--to=chrubis@suse.cz \
--cc=Markos.Chandras@imgtec.com \
--cc=ltp-list@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.