From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] igmpproxy: uclinux support merged upstream
Date: Thu, 19 May 2016 16:03:59 +0200 [thread overview]
Message-ID: <20160519160359.4fa32ca2@free-electrons.com> (raw)
In-Reply-To: <1463661925-56795-1-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
On Thu, 19 May 2016 07:45:24 -0500, Matt Weber wrote:
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> --
> v2 -> v3
> - Upstream version bump now contains this feature
Doesn't this patch depends on PATCH 2/2 being applied?
If so, they should be a single patch, otherwise if I apply only this
patch, the build is broken.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-19 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 12:45 [Buildroot] [PATCH v3 1/2] igmpproxy: uclinux support merged upstream Matt Weber
2016-05-19 12:45 ` [Buildroot] [PATCH v3 2/2] igmpproxy: bump version to a731683d1a65956fa05024b0597b105fe6a3a122 Matt Weber
2016-05-19 12:55 ` [Buildroot] [PATCH v3 1/2] igmpproxy: uclinux support merged upstream Baruch Siach
2016-05-19 14:22 ` Matthew Weber
2016-05-19 14:03 ` 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=20160519160359.4fa32ca2@free-electrons.com \
--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