From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Paul Walmsley <paul@pwsan.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Gopinath, Thara" <thara@ti.com>,
"G, Manjunath Kondaiah" <manjugk@ti.com>
Subject: Re: [PATCH] OMAP4: hwmod data: Fix SR flags, structures order and field alignment
Date: Thu, 23 Dec 2010 15:40:11 -0800 [thread overview]
Message-ID: <20101223234011.GU7771@atomide.com> (raw)
In-Reply-To: <4D13CC21.9010109@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [101223 14:24]:
>
> >Also this patch applied (contactenated multiple patches?) turns
> >into a hard to read interleaved patch for some parts:
>
> Mmm, I do not understand how did you get that diff? This is not
> like that in the patch I sent you?
> The patch should apply cleanely on top of your omap-for-linus
> branch.
The same interleaving also showed up in year earlier branch
for some reason..
> OK, as a special gift for you, you will have 4 patches :-)
OK thanks for updating, looks good to me now.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP4: hwmod data: Fix SR flags, structures order and field alignment
Date: Thu, 23 Dec 2010 15:40:11 -0800 [thread overview]
Message-ID: <20101223234011.GU7771@atomide.com> (raw)
In-Reply-To: <4D13CC21.9010109@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [101223 14:24]:
>
> >Also this patch applied (contactenated multiple patches?) turns
> >into a hard to read interleaved patch for some parts:
>
> Mmm, I do not understand how did you get that diff? This is not
> like that in the patch I sent you?
> The patch should apply cleanely on top of your omap-for-linus
> branch.
The same interleaving also showed up in year earlier branch
for some reason..
> OK, as a special gift for you, you will have 4 patches :-)
OK thanks for updating, looks good to me now.
Tony
next prev parent reply other threads:[~2010-12-23 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 14:15 [PATCH] OMAP4: hwmod data: Fix SR flags, structures order and field alignment Benoit Cousson
2010-12-23 14:15 ` Benoit Cousson
2010-12-23 17:17 ` Kevin Hilman
2010-12-23 17:17 ` Kevin Hilman
2010-12-23 20:46 ` Tony Lindgren
2010-12-23 20:46 ` Tony Lindgren
2010-12-23 22:24 ` Cousson, Benoit
2010-12-23 22:24 ` Cousson, Benoit
2010-12-23 23:40 ` Tony Lindgren [this message]
2010-12-23 23:40 ` Tony Lindgren
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=20101223234011.GU7771@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=paul@pwsan.com \
--cc=thara@ti.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 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.