From: Bjorn Helgaas <bhelgaas@google.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] bus: mvebu-mbus: Fix incorrect size for PCI aperture resources
Date: Tue, 18 Feb 2014 13:38:01 -0700 [thread overview]
Message-ID: <20140218203801.GA8786@google.com> (raw)
In-Reply-To: <20140217013949.GE7862@titan.lakedaemon.net>
On Sun, Feb 16, 2014 at 08:39:49PM -0500, Jason Cooper wrote:
> On Fri, Feb 14, 2014 at 11:29:10AM -0700, Bjorn Helgaas wrote:
> > On Wed, Feb 12, 2014 at 03:57:07PM -0700, Jason Gunthorpe wrote:
> > > reg[0] is the DT base, reg[1] is the DT length in bytes,
> > > struct resource.end is the inclusive end address, so a -1 is
> > > required.
> > >
> > > Tested on kirkwood.
> > >
> > > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> >
> > Do these two patches need to go together? I don't maintain
> > drivers/bus/mvebu-mbus.c, but if these should be kept together, I'd be
> > happy to merge them both, given the appropriate ack from Jason C or Thomas.
>
> I have one small change for mvebu-mbus queued up, which won't conflict
> here. Please take both:
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
I added the acks and applied both patches to pci/host-mvebu for v3.15,
thanks!
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: bhelgaas@google.com (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] bus: mvebu-mbus: Fix incorrect size for PCI aperture resources
Date: Tue, 18 Feb 2014 13:38:01 -0700 [thread overview]
Message-ID: <20140218203801.GA8786@google.com> (raw)
In-Reply-To: <20140217013949.GE7862@titan.lakedaemon.net>
On Sun, Feb 16, 2014 at 08:39:49PM -0500, Jason Cooper wrote:
> On Fri, Feb 14, 2014 at 11:29:10AM -0700, Bjorn Helgaas wrote:
> > On Wed, Feb 12, 2014 at 03:57:07PM -0700, Jason Gunthorpe wrote:
> > > reg[0] is the DT base, reg[1] is the DT length in bytes,
> > > struct resource.end is the inclusive end address, so a -1 is
> > > required.
> > >
> > > Tested on kirkwood.
> > >
> > > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> >
> > Do these two patches need to go together? I don't maintain
> > drivers/bus/mvebu-mbus.c, but if these should be kept together, I'd be
> > happy to merge them both, given the appropriate ack from Jason C or Thomas.
>
> I have one small change for mvebu-mbus queued up, which won't conflict
> here. Please take both:
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
I added the acks and applied both patches to pci/host-mvebu for v3.15,
thanks!
Bjorn
next prev parent reply other threads:[~2014-02-18 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 22:57 [PATCH 1/2] bus: mvebu-mbus: Fix incorrect size for PCI aperture resources Jason Gunthorpe
2014-02-12 22:57 ` Jason Gunthorpe
2014-02-12 22:57 ` [PATCH 2/2] PCI: mvebu - Call request_resources on the apertures Jason Gunthorpe
2014-02-12 22:57 ` Jason Gunthorpe
2014-02-12 23:24 ` Arnd Bergmann
2014-02-12 23:24 ` Arnd Bergmann
2014-02-12 23:22 ` [PATCH 1/2] bus: mvebu-mbus: Fix incorrect size for PCI aperture resources Arnd Bergmann
2014-02-12 23:22 ` Arnd Bergmann
2014-02-14 18:29 ` Bjorn Helgaas
2014-02-14 18:29 ` Bjorn Helgaas
2014-02-17 1:39 ` Jason Cooper
2014-02-17 1:39 ` Jason Cooper
2014-02-18 20:38 ` Bjorn Helgaas [this message]
2014-02-18 20:38 ` Bjorn Helgaas
2014-02-18 17:05 ` Jason Gunthorpe
2014-02-18 17:05 ` Jason Gunthorpe
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=20140218203801.GA8786@google.com \
--to=bhelgaas@google.com \
--cc=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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 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.