From: Josh Cartwright <joshc@eso.teric.us>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] macb: rename platform data
Date: Tue, 26 Mar 2013 10:21:09 -0500 [thread overview]
Message-ID: <20130326152109.GH16050@kryptos> (raw)
In-Reply-To: <20130325091247.GW1906@pengutronix.de>
On Mon, Mar 25, 2013 at 10:12:47AM +0100, Sascha Hauer wrote:
> Hi Josh,
>
> On Tue, Mar 19, 2013 at 10:54:32AM -0500, Josh Cartwright wrote:
> > On Fri, Mar 15, 2013 at 06:26:00PM -0500, Josh Cartwright wrote:
> > [..]
> > > >From 0d51dc731ff3934e22e78405a992658a8d3bf1de Mon Sep 17 00:00:00 2001
> > > From: Josh Cartwright <joshc@eso.teric.us>
> > > Date: Tue, 19 Mar 2013 10:22:48 -0500
> > > Subject: [PATCH] parameter: fix build warning when !CONFIG_PARAMETER
> > > To: barebox@lists.infradead.org
> >
> > Ugh, sorry that I butchered patch submission and this mail ended up with
> > two patches together; should I resend?
>
> No, it's ok. I applied the macb pdata rename. If you wish to have the
> other one applied, please resend this one.
It looks like what was applied to your tree was a squash of these two
changes together, so no need to resend. I'll be more careful in the
future.
Thanks,
Josh
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-03-26 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 23:26 [PATCH] macb: rename platform data Josh Cartwright
2013-03-19 15:54 ` Josh Cartwright
2013-03-25 9:12 ` Sascha Hauer
2013-03-26 15:21 ` Josh Cartwright [this message]
2013-03-27 8:31 ` Sascha Hauer
2013-03-19 15:22 ` [PATCH RESEND] parameter: fix build warning when !CONFIG_PARAMETER Josh Cartwright
2013-04-02 6:29 ` 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=20130326152109.GH16050@kryptos \
--to=joshc@eso.teric.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.