All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, klebers@linux.vnet.ibm.com,
	lucaskt@linux.vnet.ibm.com, bhelgaas@google.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] pci: Export pci_dev_type
Date: Fri, 5 Apr 2013 17:55:33 +1100	[thread overview]
Message-ID: <20130405065533.GD5082@concordia> (raw)
In-Reply-To: <201304042158.r34LwDHx010466@d03av02.boulder.ibm.com>

Hi Bjorn,

Should we take this series via the powerpc tree, assuming you're OK with
this patch?

cheers

On Thu, Apr 04, 2013 at 04:58:13PM -0500, Brian King wrote:
> 
> Export pci_dev_type so that arch specific PCI probing code can
> initialize a new PCI device struct.
> 
> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
> ---
> 
>  drivers/pci/pci.h   |    1 -
>  include/linux/pci.h |    1 +
>  2 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN drivers/pci/pci.h~pci_export_pci_dev_type drivers/pci/pci.h
> --- linux/drivers/pci/pci.h~pci_export_pci_dev_type	2013-04-02 17:01:25.000000000 -0500
> +++ linux-bjking1/drivers/pci/pci.h	2013-04-02 17:02:31.000000000 -0500
> @@ -153,7 +153,6 @@ static inline int pci_no_d1d2(struct pci
>  }
>  extern struct device_attribute pci_dev_attrs[];
>  extern struct device_attribute pcibus_dev_attrs[];
> -extern struct device_type pci_dev_type;
>  extern struct bus_attribute pci_bus_attrs[];
>  
>  
> diff -puN include/linux/pci.h~pci_export_pci_dev_type include/linux/pci.h
> --- linux/include/linux/pci.h~pci_export_pci_dev_type	2013-04-02 17:01:59.000000000 -0500
> +++ linux-bjking1/include/linux/pci.h	2013-04-02 17:02:29.000000000 -0500
> @@ -670,6 +670,7 @@ enum pcie_bus_config_types {
>  extern enum pcie_bus_config_types pcie_bus_config;
>  
>  extern struct bus_type pci_bus_type;
> +extern struct device_type pci_dev_type;
>  
>  /* Do NOT directly access these two variables, unless you are arch specific pci
>   * code, or pci core code. */
> _
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
> 

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: klebers@linux.vnet.ibm.com, linux-pci@vger.kernel.org,
	bhelgaas@google.com, linuxppc-dev@lists.ozlabs.org,
	lucaskt@linux.vnet.ibm.com
Subject: Re: [PATCH 1/3] pci: Export pci_dev_type
Date: Fri, 5 Apr 2013 17:55:33 +1100	[thread overview]
Message-ID: <20130405065533.GD5082@concordia> (raw)
In-Reply-To: <201304042158.r34LwDHx010466@d03av02.boulder.ibm.com>

Hi Bjorn,

Should we take this series via the powerpc tree, assuming you're OK with
this patch?

cheers

On Thu, Apr 04, 2013 at 04:58:13PM -0500, Brian King wrote:
> 
> Export pci_dev_type so that arch specific PCI probing code can
> initialize a new PCI device struct.
> 
> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
> ---
> 
>  drivers/pci/pci.h   |    1 -
>  include/linux/pci.h |    1 +
>  2 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN drivers/pci/pci.h~pci_export_pci_dev_type drivers/pci/pci.h
> --- linux/drivers/pci/pci.h~pci_export_pci_dev_type	2013-04-02 17:01:25.000000000 -0500
> +++ linux-bjking1/drivers/pci/pci.h	2013-04-02 17:02:31.000000000 -0500
> @@ -153,7 +153,6 @@ static inline int pci_no_d1d2(struct pci
>  }
>  extern struct device_attribute pci_dev_attrs[];
>  extern struct device_attribute pcibus_dev_attrs[];
> -extern struct device_type pci_dev_type;
>  extern struct bus_attribute pci_bus_attrs[];
>  
>  
> diff -puN include/linux/pci.h~pci_export_pci_dev_type include/linux/pci.h
> --- linux/include/linux/pci.h~pci_export_pci_dev_type	2013-04-02 17:01:59.000000000 -0500
> +++ linux-bjking1/include/linux/pci.h	2013-04-02 17:02:29.000000000 -0500
> @@ -670,6 +670,7 @@ enum pcie_bus_config_types {
>  extern enum pcie_bus_config_types pcie_bus_config;
>  
>  extern struct bus_type pci_bus_type;
> +extern struct device_type pci_dev_type;
>  
>  /* Do NOT directly access these two variables, unless you are arch specific pci
>   * code, or pci core code. */
> _
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
> 

  reply	other threads:[~2013-04-05  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 21:58 [PATCH 1/3] pci: Export pci_dev_type Brian King
2013-04-04 21:58 ` Brian King
2013-04-05  6:55 ` Michael Ellerman [this message]
2013-04-05  6:55   ` Michael Ellerman

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=20130405065533.GD5082@concordia \
    --to=michael@ellerman.id.au \
    --cc=bhelgaas@google.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=klebers@linux.vnet.ibm.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lucaskt@linux.vnet.ibm.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.