All of lore.kernel.org
 help / color / mirror / Atom feed
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL][for 3.5] pull request of board-specific branch in arch-pxa git tree
Date: Fri, 18 May 2012 11:56:43 +0200	[thread overview]
Message-ID: <20120518095643.GG12015@sortiz-mobl> (raw)
In-Reply-To: <201205151140.07655.arnd@arndb.de>

Hi Arnd, Paul,

On Tue, May 15, 2012 at 11:40:07AM +0000, Arnd Bergmann wrote:
> On Tuesday 15 May 2012, Paul Parsons wrote:
> > --- On Tue, 15/5/12, Arnd Bergmann <arnd@arndb.de> wrote:
> 
> > > 
> > > Did you miss a dependency? Should I revert that patch for
> > > now?
> > 
> > hx4700.c expects to find the clock_rate field in the
> > asic3_platform_data structure.
> > 
> > The clock_rate field is due to be added in V3.5:
> > 
> > http://lkml.indiana.edu/hypermail/linux/kernel/1204.2/00339.html
> > 
> 
> This is not good, you should not split patches in a way that breaks
> the individual pieces. It would have been better to just take the entire
> patch through either arm-soc or the mfd tree.
> 
> Any suggestions for a way out of this mess? I'm inclined to just
> revert the patch I have and let Samuel pick it up to submit it along
> with the other half.
That sounds reasonable. However, it's too late now for a 3.5 inclusion, so
I'll queue it to my for-next branch.
Paul, could you please re-send this patch to me ?

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2012-05-18  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  2:22 [GIT PULL][for 3.5] pull request of board-specific branch in arch-pxa git tree Haojian Zhuang
2012-05-09  9:51 ` Olof Johansson
2012-05-15  9:25 ` Arnd Bergmann
2012-05-15  9:32   ` Paul Parsons
2012-05-15 11:40     ` Arnd Bergmann
2012-05-15 12:22       ` Paul Parsons
2012-05-15 12:28         ` Arnd Bergmann
2012-05-18  9:56       ` Samuel Ortiz [this message]

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=20120518095643.GG12015@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.