From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Denis Efremov <efremov@linux.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] spark/PCI: Remove HAVE_ARCH_PCI_RESOURCE_TO_USER
Date: Sun, 28 Jul 2019 22:25:18 +0200 [thread overview]
Message-ID: <db0f3329-898b-d018-a5ed-cd7bdbd649bf@physik.fu-berlin.de> (raw)
In-Reply-To: <20190728202213.15550-6-efremov@linux.com>
Hi Denis!
On 7/28/19 10:22 PM, Denis Efremov wrote:
> The function pci_resource_to_user() was turned to a weak one. Thus,
> spark-specific version will automatically override the generic one
> and the HAVE_ARCH_PCI_RESOURCE_TO_USER macro should be removed.
Typo, it should be "sparc/PCI" in the subject and "sparc-specific"
in the commit description.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2019-07-28 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 20:22 [PATCH 0/5] PCI: Convert pci_resource_to_user() to a weak function Denis Efremov
2019-07-28 20:22 ` [PATCH 1/5] PCI: Convert pci_resource_to_user " Denis Efremov
2019-07-28 22:49 ` [EXTERNAL][PATCH " Paul Burton
2019-07-29 6:31 ` Joe Perches
2019-07-29 10:06 ` Denis Efremov
2019-07-28 20:22 ` [PATCH 2/5] microblaze/PCI: Remove HAVE_ARCH_PCI_RESOURCE_TO_USER Denis Efremov
2019-07-28 20:22 ` [PATCH 3/5] mips/PCI: " Denis Efremov
2019-07-28 20:22 ` [PATCH 4/5] powerpc/PCI: " Denis Efremov
2019-07-28 20:22 ` [PATCH 5/5] spark/PCI: " Denis Efremov
2019-07-28 20:25 ` John Paul Adrian Glaubitz [this message]
2019-07-28 21:17 ` Denis Efremov
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=db0f3329-898b-d018-a5ed-cd7bdbd649bf@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=efremov@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®