linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: treding@nvidia.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 pci_iomap, was: Re: next build: 258 warnings 9 failures (next/next-20141119)
Date: Wed, 19 Nov 2014 15:20:10 +0100	[thread overview]
Message-ID: <20141119142009.GA3488@ulmo.nvidia.com> (raw)
In-Reply-To: <3897871.0i8K9av6A3@wuerfel>

On Wed, Nov 19, 2014 at 03:11:03PM +0100, Arnd Bergmann wrote:
> On Wednesday 19 November 2014 14:56:42 Thierry Reding wrote:
> > 
> > Oops, I just looked at that file on my system and I already have the
> > select GENERIC_PCI_IOMAP exactly where you have it. Turns out I have
> > that same patch, albeit with a somewhat obfuscated name in my tree
> > but never got around to clean up the commit message or sending it out.
> > 
> > Do you want to apply that patch on top or shall I redo the pull request
> > with that patch folded in so we can keep bisectability across the
> > series?
> 
> I would prefer to have my patch applied on top so I don't have to redo
> the merge between your patches and Will's patches.

Okay.

> Can you confirm that you have no further patches that I might need?

Yes, I have no other patches asm-generic related patches.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141119/422f7251/attachment.sig>

      reply	other threads:[~2014-11-19 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <546c75d7.6336460a.14b5.474d@mx.google.com>
2014-11-19 11:15 ` arm64 pci_iomap, was: Re: next build: 258 warnings 9 failures (next/next-20141119) Arnd Bergmann
2014-11-19 13:56   ` Thierry Reding
2014-11-19 14:11     ` Arnd Bergmann
2014-11-19 14:20       ` Thierry Reding [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=20141119142009.GA3488@ulmo.nvidia.com \
    --to=treding@nvidia.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).