linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: discuss@x86-64.org, dev-etrax@axis.com,
	linux-ia64@vger.kernel.org, chris@zankel.net,
	Greg Kroah-Hartman <greg@kroah.com>,
	linux-m68k@vger.kernel.org, uclinux-v850@lsi.nec.co.jp,
	linuxppc-dev@ozlabs.org, linux-mips@linux-mips.org,
	gerg@uclinux.org, sparclinux@vger.kernel.org,
	ink@jurassic.park.msu.ru, linux-pci@atrey.karlin.mff.cuni.cz,
	rth@twiddle.net, kernel@wantstofly.org,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] [PATCH 2/2] Make pcibios_add_platform_entries() return errors
Date: Wed, 07 Mar 2007 09:55:18 +0100	[thread overview]
Message-ID: <1173257718.5101.16.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <1173204301.3379.33.camel@mulgrave.il.steeleye.com>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

On Tue, 2007-03-06 at 12:05 -0600, James Bottomley wrote:
> On Tue, 2007-03-06 at 16:06 +0100, Michael Ellerman wrote:
> >  int __must_check pci_create_sysfs_dev_files (struct pci_dev *pdev)
> > @@ -644,10 +644,13 @@ int __must_check pci_create_sysfs_dev_fi
> >  		}
> >  	}
> >  	/* add platform-specific attributes */
> > -	pcibios_add_platform_entries(pdev);
> > +	if (pcibios_add_platform_entries(pdev))
> > +		goto err_rom_attr;
> >  
> >  	return 0;
> >  
> > +err_rom_attr:
> > +	sysfs_remove_bin_file(&pdev->dev.kobj, rom_attr);
> 
> This file is only created if the rom resource has a non-zero length.  If
> you unconditionally call sysfs_remove_bin_file() it's going to spit
> scary warnings and dump traces in this error leg if the rom resource
> doesn't exist.

Ah crud, don't write patches during meetings. I'll send a fixed version.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-03-07  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 15:06 [PATCH 1/2] Use a weak symbol for the empty version of pcibios_add_platform_entries() Michael Ellerman
2007-03-06 15:06 ` [PATCH 2/2] Make pcibios_add_platform_entries() return errors Michael Ellerman
2007-03-06 18:05   ` [parisc-linux] " James Bottomley
2007-03-07  8:55     ` Michael Ellerman [this message]
2007-03-06 18:01 ` [parisc-linux] [PATCH 1/2] Use a weak symbol for the empty version of pcibios_add_platform_entries() James Bottomley

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=1173257718.5101.16.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=James.Bottomley@SteelEye.com \
    --cc=chris@zankel.net \
    --cc=dev-etrax@axis.com \
    --cc=discuss@x86-64.org \
    --cc=gerg@uclinux.org \
    --cc=greg@kroah.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kernel@wantstofly.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=rth@twiddle.net \
    --cc=sparclinux@vger.kernel.org \
    --cc=uclinux-v850@lsi.nec.co.jp \
    /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).