mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: akpm@linux-foundation.org, jbeulich@novell.com, gregkh@suse.de,
	jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org,
	dhowells@redhat.com, yasutake.koichi@jp.panasonic.com
Subject: Re: [PATCH] PCI: remove pci_dac_dma_... APIs on mn10300
Date: Mon, 29 Jun 2009 12:20:21 -0700	[thread overview]
Message-ID: <20090629122021.1c2b01fa@jbarnes-g45> (raw)
In-Reply-To: <4A44321D.3070007@oss.ntt.co.jp>

On Fri, 26 Jun 2009 11:27:41 +0900
Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> wrote:

> It seems that mn10300 made it upstream after Jan Beulich's
> pci_dac_dma_* cleanup work and still defines pci_dac_dma_supported().
> This API is not required by the PCI subsystem anymore, so remove it.
> 
> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
> ---
> 
> diff -urNp linux-2.6.31-rc1-orig/arch/mn10300/include/asm/pci.h
> linux-2.6.31-rc1/arch/mn10300/include/asm/pci.h ---
> linux-2.6.31-rc1-orig/arch/mn10300/include/asm/pci.h
> 2009-06-26 10:58:02.012044068 +0900 +++
> linux-2.6.31-rc1/arch/mn10300/include/asm/pci.h	2009-06-26
> 11:19:34.130867667 +0900 @@ -70,10 +70,6 @@ struct pci_dev; */
> #define PCI_DMA_BUS_IS_PHYS	(1)
> 
> -
> -/* This is always fine. */
> -#define pci_dac_dma_supported(pci_dev, mask)	(0)
> -
>   /* Return the index of the PCI controller for device. */
>   static inline int pci_controller_num(struct pci_dev *dev)
>   {

Had to fix up some fuzz, but it's now in my for-linus branch.  Thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2009-06-29 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  5:08 Fernando Luis Vázquez Cao
2008-12-09 22:55 ` Jesse Barnes
2009-06-26  2:26 ` Fernando Luis Vázquez Cao
2009-06-26  2:27   ` Fernando Luis Vázquez Cao
2009-06-29 19:20     ` Jesse Barnes [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=20090629122021.1c2b01fa@jbarnes-g45 \
    --to=jesse.barnes@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=gregkh@suse.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yasutake.koichi@jp.panasonic.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 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®