From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Andrew Lentvorski <bsder@allcaps.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org
Subject: Re: Bug on configure ... where to report?
Date: Tue, 03 Mar 2015 07:12:42 +0100 [thread overview]
Message-ID: <54F550DA.3010601@hartkopp.net> (raw)
In-Reply-To: <54F4EAE3.5090406@allcaps.org>
On 03/02/2015 11:57 PM, Andrew Lentvorski wrote:
> Tried the patch but got this (what am I missing to apply this?):
>
> root@beaglebone:~/can-utils# git apply makefile-patch.diff
> fatal: patch with only garbage at line 5
>
> root@beaglebone:~/can-utils# patch <makefile-patch.diff
> patch: **** Only garbage was found in the patch input.
>
> root@beaglebone:~/can-utils# cat makefile-patch.diff
> diff --git a/GNUmakefile.am b/GNUmakefile.am
> index 53dfb4ec47db..580e60d364c2 100644
> --- a/GNUmakefile.am
> +++ b/GNUmakefile.am
> <at> <at> -1,3 +1,5 <at> <at>
Your mail client obviously mangled the content :-(
'<at>' has to be '@' of course ...
You may check the content from the mailing list archive:
http://marc.info/?l=linux-can&m=142494031528060&w=2
[Download message RAW] ->
http://marc.info/?l=linux-can&m=142494031528060&q=raw
Just save this link as file and try to apply that file.
cd can-utils
patch -p1 < downloaded.patch
I tested this approach and it worked.
Regards,
Oliver
next prev parent reply other threads:[~2015-03-03 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 0:07 Bug on configure ... where to report? Andrew Lentvorski
2015-02-26 8:45 ` Marc Kleine-Budde
2015-03-02 22:57 ` Andrew Lentvorski
2015-03-03 6:12 ` Oliver Hartkopp [this message]
2015-03-03 7:06 ` Andrew Lentvorski
2015-03-03 7:29 ` Marc Kleine-Budde
2015-03-03 10:30 ` Andrew Lentvorski
2015-02-26 8:47 ` Marc Kleine-Budde
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=54F550DA.3010601@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=bsder@allcaps.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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.