From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/23] ARM: plat-omap: remove arch specific special handling for ioremap
Date: Mon, 5 Dec 2011 20:46:23 -0800 [thread overview]
Message-ID: <20111206044622.GD31337@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1112052246030.2357@xanadu.home>
* Nicolas Pitre <nico@fluxnic.net> [111205 19:37]:
> On Tue, 6 Dec 2011, Russell King - ARM Linux wrote:
> > On Mon, Dec 05, 2011 at 11:56:09PM +0000, Russell King - ARM Linux wrote:
> > > On Fri, Dec 02, 2011 at 04:39:31PM -0500, Nicolas Pitre wrote:
> > > > OK, thanks for testing. Since Russell didn't commit this to his stable
> > > > branch yet I simply folded in your fix and added your tested-by tag.
> > >
> > > So I'm about to push what I had out in the devel-stable branch... what
> > > am I supposed to do with this?
> >
> > Okay, yet again I find myself having to wait hours for a reply - which
> > I expect will be forthcoming sometime tomorrow afternoon my time. If
> > I wait, it means a delay of another 24 hours before I push my tree out.
> >
> > This is not acceptable.
>
> You asked at 11:56:09PM +0000.
> I replied at 19:33:34 -0500.
> That's a delay of 37 minutes 25 seconds.
> I even received my reply back from the mailing list server at
> 19:39:37 -0500 so hopefully you must have received it within the hour.
> Granted, you merged my branch at 23:27:59 +0000 so I hadn't replied yet.
>
> However, the commit says:
>
> Merge: 742eaa6a6e 0af362f844
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> AuthorDate: Mon Dec 5 23:27:54 2011 +0000
> Commit: Russell King <rmk+kernel@arm.linux.org.uk>
> CommitDate: Mon Dec 5 23:27:59 2011 +0000
>
> Merge branch 'vmalloc' of git://git.linaro.org/people/nico/linux into devel-stable
>
> So the commit message is written as if you pulled my branch directly
> instead of a local branch, however my repo was already updated by that
> time. In fact it was updated 2 days ago. Strangely enough, you still
> have a version prior to that last update.
>
> > So I'm pushing my tree out as-is - which means the stuff I pulled
> > previously is now frozen.
>
> That's not a big problem.
>
> Tony: could you please send your original patch directly to Russell with
> my ACK?
OK, acked with your Linaro address as with your other patches in the
series. It's patch 7192/1.
Regards,
Tony
next prev parent reply other threads:[~2011-12-06 4:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 5:48 [PATCH 0/23] mach/vmalloc.h removal, and ioremap optimization Nicolas Pitre
2011-11-16 5:48 ` [PATCH 01/23] ARM: mach-dove: remove inclusion of <mach/vmalloc.h> Nicolas Pitre
2011-11-16 5:48 ` [PATCH 02/23] ARM: mach-prima2: don't define SIRFSOC_VA in terms of VMALLOC_END Nicolas Pitre
2011-11-16 5:48 ` [PATCH 03/23] ARM: plat-mxc: remove inclusion of <mach/vmalloc.h> Nicolas Pitre
2011-11-16 5:48 ` [PATCH 04/23] ARM: mach-at91: remove arch specific special handling for ioremap Nicolas Pitre
2011-11-16 5:48 ` [PATCH 05/23] ARM: mach-davinci: " Nicolas Pitre
2011-11-16 5:48 ` [PATCH 06/23] ARM: mach-tegra: " Nicolas Pitre
2011-11-16 5:48 ` [PATCH 07/23] ARM: plat-omap: " Nicolas Pitre
2011-11-18 18:39 ` Kevin Hilman
2011-12-02 20:21 ` Tony Lindgren
2011-12-02 21:39 ` Nicolas Pitre
2011-12-05 23:21 ` Tony Lindgren
2011-12-05 23:56 ` Russell King - ARM Linux
2011-12-06 0:33 ` Nicolas Pitre
2011-12-06 0:36 ` Russell King - ARM Linux
2011-12-06 4:09 ` Nicolas Pitre
2011-12-06 4:46 ` Tony Lindgren [this message]
2011-12-06 8:55 ` Russell King - ARM Linux
2011-11-16 5:48 ` [PATCH 08/23] ARM: mach-bcmring: use proper constant to identify DMA memory area Nicolas Pitre
2011-11-16 5:48 ` [PATCH 09/23] ARM: mach-orion5x: remove arch specific special handling for ioremap Nicolas Pitre
2011-11-16 5:48 ` [PATCH 10/23] ARM: mach-kirkwood: " Nicolas Pitre
2011-11-16 5:48 ` [PATCH 11/23] ARM: mach-ixp23xx: " Nicolas Pitre
2011-11-18 0:03 ` Deepak Saxena
2011-11-16 5:48 ` [PATCH 12/23] ARM: plat-iop: " Nicolas Pitre
2011-11-16 5:48 ` [PATCH 13/23] ARM: versatile: remove overlapping map_desc entry Nicolas Pitre
2011-11-16 5:48 ` [PATCH 14/23] ARM: realview: fix map_desc alignment Nicolas Pitre
2011-11-16 5:48 ` [PATCH 15/23] ARM: realview-eb11mp: " Nicolas Pitre
2011-11-16 5:48 ` [PATCH 16/23] ARM: sort the meminfo array earlier Nicolas Pitre
2011-11-16 5:48 ` [PATCH 17/23] ARM: move initialization of the high_memory variable earlier Nicolas Pitre
2011-11-16 5:48 ` [PATCH 18/23] mm: add vm_area_add_early() Nicolas Pitre
2011-11-16 5:48 ` [PATCH 19/23] ARM: move iotable mappings within the vmalloc region Nicolas Pitre
2011-11-16 5:48 ` [PATCH 20/23] ARM: simplify __iounmap() when dealing with section based mapping Nicolas Pitre
2011-11-16 5:48 ` [PATCH 21/23] ARM: add generic ioremap optimization by reusing static mappings Nicolas Pitre
2011-11-22 10:16 ` Russell King - ARM Linux
2011-11-22 13:44 ` Nicolas Pitre
2011-11-16 5:48 ` [PATCH 22/23] ARM: big removal of now unused vmalloc.h files Nicolas Pitre
2011-11-16 5:48 ` [PATCH 23/23] ARM: move VMALLOC_END down temporarily for shmobile Nicolas Pitre
2011-12-16 5:34 ` Magnus Damm
2011-12-17 16:41 ` Nicolas Pitre
2011-11-16 17:13 ` [PATCH 0/23] mach/vmalloc.h removal, and ioremap optimization Stephen Warren
2011-11-16 23:08 ` Nicolas Pitre
2011-11-18 10:04 ` Jamie Iles
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=20111206044622.GD31337@atomide.com \
--to=tony@atomide.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 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).