From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mtd: add patch to fix host build error with gcc 5.1
Date: Tue, 26 May 2015 13:20:11 +0300 [thread overview]
Message-ID: <20150526102011.GR2260@tarshish> (raw)
In-Reply-To: <1432635054.24186.3.camel@embedded.rocks>
Hi J?rg,
On Tue, May 26, 2015 at 12:10:54PM +0200, J?rg Krause wrote:
> On Di, 2015-05-26 at 12:57 +0300, Baruch Siach wrote:
> > What is the upstream status of this patch?
>
> Good question! I've seen now that Bernard Walle submitted the same
> patch three weeks ago to the mtd mailing list [1]. No feedback so far.
>
> [1]
> https://patchwork.ozlabs.org/patch/467254/
Great. Please add this information to the commit log and the patch
description.
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-05-26 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 9:53 [Buildroot] [PATCH 1/1] package/mtd: add patch to fix host build error with gcc 5.1 Jörg Krause
2015-05-26 9:57 ` Baruch Siach
2015-05-26 10:10 ` Jörg Krause
2015-05-26 10:20 ` Baruch Siach [this message]
2015-05-26 10:28 ` Jörg Krause
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=20150526102011.GR2260@tarshish \
--to=baruch@tkos.co.il \
--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