From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Binary patches
Date: Mon, 28 Jan 2013 13:19:37 +0000 [thread overview]
Message-ID: <emaf3af07a-4ae2-422a-8881-4f00e80256b8@nb-mak> (raw)
In-Reply-To: <em468d5351-2acd-4e35-83ac-ac0c19cb3a7d@nb-mak>
[-- Attachment #1.1: Type: text/plain, Size: 593 bytes --]
Does anyone have a tip howto make a binary patch for ptxdist ?
------ Originalnachricht ------
Von: "Matthias Klein" <matthias.klein@optimeas.de>
An: ptxdist@pengutronix.de
Gesendet: 23.01.2013 11:54:55
Betreff: [ptxdist] Binary patches
>Hello,
>
>I try to create a patch file for the kernel which adds a binary file
>(firmware blob).
>I tried git diff --binary but then I get following error from patch:
>
>applying 'firmware.diff'
>patch: **** Only garbage was found in the patch input.
>
>How can I create a patch for binary files?
>
>
>Best regards,
>
>Matthias
>
[-- Attachment #1.2: Type: text/html, Size: 1958 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-28 13:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 10:54 Matthias Klein
2013-01-28 13:19 ` Matthias Klein [this message]
2013-01-28 14:31 ` Andreas Bießmann
2013-01-28 14:38 ` Matthias Klein
2013-01-28 15:06 ` Andreas Bießmann
2013-01-29 8:39 ` Matthias Klein
2013-01-29 9:58 ` Andreas Bießmann
2013-01-29 10:20 ` Juergen Beisert
2013-01-29 10:26 ` Matthias Klein
2013-01-29 11:12 ` Andreas Bießmann
2013-01-29 12:06 ` Bernhard Walle
2013-01-29 12:30 ` Bernhard Walle
2013-01-29 13:29 ` Andreas Bießmann
2013-01-29 13:40 ` Bernhard Walle
2013-01-29 10:29 ` Bernhard Walle
2013-01-28 19:14 ` Robert Schwebel
2013-01-29 13:12 ` Bernhard Walle
2013-01-29 13:45 ` Matthias Klein
2013-01-31 10:32 ` Alexander Stein
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=emaf3af07a-4ae2-422a-8881-4f00e80256b8@nb-mak \
--to=matthias.klein@optimeas.de \
--cc=ptxdist@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox