linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-mmc@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Ludovic Desroches <ludovic.desroches@atmel.com>,
	Chris Ball <cjb@laptop.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL v2] at91: fixes for 3.7-rc7
Date: Tue, 20 Nov 2012 23:03:03 -0800	[thread overview]
Message-ID: <20121121070303.GD7615@quad.lixom.net> (raw)
In-Reply-To: <50AB466F.5010500@atmel.com>

Hi,


On Tue, Nov 20, 2012 at 09:59:27AM +0100, Nicolas Ferre wrote:
> Arnd, Olof,
> 
> Just for the record, I do not want to put pressure at a such late time in
> the 3.7-rc process. So, I just reworked that pull-request because the previous
> one was wrong:
> - wrong patch content (DT nodes with wrong size)
> - not all tags in patches (Jean-Christophe and Arnd tags were missing...)
> 
> Just to start from a sane base if I have to rebase this work for 3.8, I let you know
> that I have updated this tag...
> 
> The following changes since commit 641f3ce64b050961d454a0716bb6dbf528315aac:
> 
>   ARM: at91/usbh: fix overcurrent gpio setup (2012-11-16 10:46:29 +0100)
> 
> are available in the git repository at:
> 
>   git://github.com/at91linux/linux-at91.git tags/at91-fixes

The new patches seem to belong in an at91/dt branch, not in a fixes one.

I can pull in the previous fixes branch as an at91/fixes-non-critical for 3.8
if you want. There's no need to rebase them for this, is there? What is the
pinctrl dependency that you are talking about, are some of these patches needed
as prerequisites for pinctrl changes or the other way around?

Sorry if I've missed more elaborate emails on this and are asking repeat
questions. ;)

-Olof

  reply	other threads:[~2012-11-21  7:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 16:31 [GIT PULL] at91: fixes for 3.7-rc7 Nicolas Ferre
2012-11-19 16:52 ` Olof Johansson
2012-11-19 17:29   ` Nicolas Ferre
2012-11-20  8:59     ` [GIT PULL v2] " Nicolas Ferre
2012-11-21  7:03       ` Olof Johansson [this message]
2012-11-21 11:25         ` Nicolas Ferre
2012-11-20 18:47     ` [GIT PULL] " Linus Walleij
2012-11-20 20:00       ` Jean-Christophe PLAGNIOL-VILLARD

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=20121121070303.GD7615@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --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;
as well as URLs for NNTP newsgroup(s).