mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@kymetacorp.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/2] environment: Support env from file in a file-system via device tree
Date: Thu, 17 Dec 2015 00:31:55 +0000	[thread overview]
Message-ID: <1450312315.26955.187.camel@rtred1test09.kymeta.local> (raw)
In-Reply-To: <20151216105214.GV11966@pengutronix.de>

On Wed, 2015-12-16 at 11:52 +0100, Sascha Hauer wrote:
> On Fri, Dec 11, 2015 at 10:37:34PM +0000, Trent Piepho wrote:
> > From d8f4428244b3c7009a6ef7d5a97a00747cd19472 Mon Sep 17 00:00:00 2001
> > From: Trent Piepho <tpiepho@kymetacorp.com>
> > Date: Fri, 11 Dec 2015 14:19:34 -0800
> > Subject: [PATCH 2/2] socfpga: Find partition with environment via device tree
> 
> The subject in this mail is wrong. The correct subject is here, but 'git
> am' takes the one from the mail.

IMAP and POP aren't supported at work so I can't use git send-email and
must instead manually import the patches into a mailer that supports
EWS.  I must have forgotten to copy the subject on that one.

> I thought over it and I am fine with the approach of putting the
> filename as an additional property into the barebox,environment node.
> 
> Also I am fine with the "of_path: Fix bug with partitions, simply code"
> patch, only I can not find the commitish that broke the partition code.

I used my local rebased branch by mistake, it should have been
75b682795eafb2385556a9642f09e0af96a1264a 

> I somewhat lost track over your outstanding patches. Could you resend
> all of them in a single series?

Ok. Have you considered using patchwork for this list?  I've found it
pretty useful for keeping track of patches.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-12-17  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 22:32 Trent Piepho
2015-12-11 22:37 ` Trent Piepho
2015-12-16 10:52   ` Sascha Hauer
2015-12-17  0:31     ` Trent Piepho [this message]
2015-12-17 10:12       ` 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=1450312315.26955.187.camel@rtred1test09.kymeta.local \
    --to=tpiepho@kymetacorp.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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