From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] snort: fix build on sparc v8
Date: Sun, 13 May 2018 21:45:50 +0200 [thread overview]
Message-ID: <20180513214550.529cba8c@windsurf.home> (raw)
In-Reply-To: <20180510111748.26293-1-fontaine.fabrice@gmail.com>
Hello,
+Sergio in Cc.
On Thu, 10 May 2018 13:17:48 +0200, Fabrice Fontaine wrote:
> Add patch to remove -mcpu=v9 before checking sparc architecture
>
> Fixes:
> - http://autobuild.buildroot.net/results/59625daa154e3136171dcb89bdc3b8b31dc85021
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/snort/0005-fix-sparc.patch | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 package/snort/0005-fix-sparc.patch
I would have preferred a Git-formatted patch, because the 4 existing
patches on the snort package are Git-formatted.
However, I haven't been able to find an upstream Git repository for
Snort, so I'm wondering how the existing Git-formatted patches have
been generated. Perhaps from a repository created locally using git
init+git add ?
Sergio, since you added the snort package, how did you generate the
patches ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-13 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 11:17 [Buildroot] [PATCH 1/1] snort: fix build on sparc v8 Fabrice Fontaine
2018-05-13 13:55 ` Yann E. MORIN
2018-05-13 19:45 ` Thomas Petazzoni [this message]
2018-05-14 16:56 ` Sergio Prado
2018-05-15 12:41 ` Thomas Petazzoni
2018-05-15 14:28 ` Sergio Prado
2018-05-15 14:59 ` Fabrice Fontaine
2018-05-15 15:14 ` Thomas Petazzoni
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=20180513214550.529cba8c@windsurf.home \
--to=thomas.petazzoni@bootlin.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