From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/2 v2] add bpkfs support
Date: Sun, 6 Oct 2013 13:34:55 +0200 [thread overview]
Message-ID: <20131006113455.GP30088@pengutronix.de> (raw)
In-Reply-To: <20131003095957.GQ32444@ns203013.ovh.net>
On Thu, Oct 03, 2013 at 11:59:57AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> Hi,
>
> v2 update comment and fix comment typo
> and rebase next
>
> The following changes since commit 705dbd7c795bbdfb448e1d0ace89d98cbceaaec1:
>
> Merge branch 'for-next/tegra' into next (2013-10-02 11:07:14 +0200)
>
> are available in the git repository at:
>
>
> git://git.jcrosoft.org/barebox.git delivery/bpkfs
>
> for you to fetch changes up to 6edfa631c4aafd71d0508b94c7cdea87695dd492:
Applied, thanks.
Please only post patches against -next when you know there are
dependencies to patches in -next. Otherwise always post them against
master as this is the branch I'll apply them on.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-10-06 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 9:59 Jean-Christophe PLAGNIOL-VILLARD
2013-10-03 10:01 ` [PATCH 1/2] filetype: add Binary PacKage BPK type Jean-Christophe PLAGNIOL-VILLARD
2013-10-03 10:01 ` [PATCH 2/2] fs: add BPKFS support Jean-Christophe PLAGNIOL-VILLARD
2013-10-06 11:34 ` Sascha Hauer [this message]
2013-10-08 12:51 ` [PATCH 0/2 v2] add bpkfs support Jean-Christophe PLAGNIOL-VILLARD
2013-10-14 9:00 ` Sascha Hauer
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=20131006113455.GP30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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