From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Matt Turner <mattst88@gmail.com>, Yinghai Lu <yinghai@kernel.org>,
linux-pci@vger.kernel.org,
linux-alpha <linux-alpha@vger.kernel.org>,
Richard Henderson <rth@twiddle.net>,
Jay Estabrook <jay.estabrook@gmail.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Some Alphas broken by f75b99d5a77d (PCI: Enforce bus address limits in resource allocation)
Date: Thu, 12 Mar 2020 20:49:58 +0000 [thread overview]
Message-ID: <20200312204958.GA20087@mail.rc.ru> (raw)
In-Reply-To: <20200312201900.GA174932@google.com>
On Thu, Mar 12, 2020 at 03:19:00PM -0500, Bjorn Helgaas wrote:
> On Wed, Mar 11, 2020 at 09:28:33PM -0700, Matt Turner wrote:
> > If the PCI bits are fine with you, I assume you'd like them to go
> > through your tree, etc? I'm perfectly happy to see the alpha bits go
> > through the same tree.
>
> Yes, I think this looks reasonable. We should get this posted in the
> usual format (commit log, signed-off-by, etc), and then get it into
> -next to see how it flies.
Ok, I'll do it this weekend.
Ivan.
prev parent reply other threads:[~2020-03-12 20:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 14:33 Some Alphas broken by f75b99d5a77d (PCI: Enforce bus address limits in resource allocation) Matt Turner
2018-04-16 21:50 ` Bjorn Helgaas
2018-04-17 4:43 ` Matt Turner
2018-04-17 19:43 ` Bjorn Helgaas
2018-04-18 20:48 ` Ivan Kokshaysky
2018-04-20 17:03 ` Bjorn Helgaas
2018-04-22 20:07 ` Matt Turner
2018-04-23 17:34 ` Ivan Kokshaysky
2018-05-02 20:33 ` Bjorn Helgaas
2018-05-02 21:10 ` Matt Turner
2018-05-07 0:46 ` Matt Turner
2019-10-18 5:57 ` Matt Turner
2020-02-22 16:55 ` Bjorn Helgaas
2020-02-28 23:51 ` Matt Turner
2020-03-01 14:30 ` Ivan Kokshaysky
2020-03-02 22:47 ` Bjorn Helgaas
2020-03-08 15:30 ` Ivan Kokshaysky
2020-03-08 19:41 ` Matt Turner
2020-03-12 4:28 ` Matt Turner
2020-03-12 20:19 ` Bjorn Helgaas
2020-03-12 20:49 ` Ivan Kokshaysky [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=20200312204958.GA20087@mail.rc.ru \
--to=ink@jurassic.park.msu.ru \
--cc=benh@kernel.crashing.org \
--cc=helgaas@kernel.org \
--cc=jay.estabrook@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=rth@twiddle.net \
--cc=yinghai@kernel.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).