[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120106083916.9588034bde22a6803e327aa9@canb.auug.org.au>
Date: Fri, 6 Jan 2012 08:39:16 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] use generic pci_iomap on all architectures
Hi Michael,
On Fri, 6 Jan 2012 08:31:41 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> [I am not *just* picking on you - others do this as well ...]
>
> On Thu, 5 Jan 2012 16:58:36 +0200 "Michael S. Tsirkin" <mst@...hat.com> wrote:
> >
> > Linus, please pull the following changes for 3.3, thanks a lot!
> >
> > These changes have been on linux-next for a while now.
> > They touch a lot of arches and have interdependencies, so merging
> > separately seems to make sense, I think.
> >
> > The following changes since commit 805a6af8dba5dfdd35ec35dc52ec0122400b2610:
> >
> > Linux 3.2 (2012-01-04 15:55:44 -0800)
>
> So why have you rebased this? All this stuff in in linux-next based on
> v3.2-rc3 since December 5 (and that version will be in linux-next today
> as well unless you update your linux-next branch in the next sort while).
OK, seems I was mistaken (and mislead by the above. Your for-linus tag
just tags what is already in linux-next and based on v3.2-rc3 ...
Sorry about that.
So why does you pull request refer to "commit
805a6af8dba5dfdd35ec35dc52ec0122400b2610", I wonder? Is that just what
"git request-pull" produced?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists