All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	rth@twiddle.net, dhowells@redhat.com, kumar.gala@freescale.com,
	davem@davemloft.net, mhw@wittsend.com, support@comtrol.com,
	Rogier Wolff <R.E.Wolff@bitwizard.nl>,
	nils@kernelconcepts.de, cjtsai@ali.com.tw,
	Lionel.Bouton@inet6.fr, benh@kernel.crashing.org,
	mchehab@brturbo.com.br, laredo@gnu.org,
	rbultje@ronald.bitfreak.net, middelin@polyware.nl, philb@gnu.org,
	tim@cyberelk.net, campbell@torque.net, andrea@suse.de,
	linux@advansys.com, chirag.kantharia@hp.com, mulix@mulix.org
Subject: Re: [PATCH] pci_find_device --> pci_get_device
Date: Tue, 19 Jul 2005 18:20:20 +0200	[thread overview]
Message-ID: <200507191820.35472@bilbo.math.uni-mannheim.de> (raw)
In-Reply-To: <42DD1FCF.4050304@gmail.com>

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

Am Dienstag, 19. Juli 2005 17:44 schrieb Jiri Slaby:
>Rolf Eike Beer napsal(a):
>>Jiri Slaby wrote:
>>>Kernel version: 2.6.13-rc3-git4
>>>
>>>* This patch removes from kernel tree pci_find_device and changes
>>>it with pci_get_device. Next, it adds pci_dev_put, to decrease reference
>>>count of the variable.
>>>* Next, there are some (about 10 or so) gcc warning problems (i. e.
>>>variable may be unitialized) solutions, which were around code with old
>>>pci_find_device.
>>
>>Is this the reason why you initialize members of static structs? If this is
>>uninitialized it will end in the bss section and will be zeroed before the
>>kernel uses is. If you do it will go into data section and add more bloat
>> to the binary. At least this is the explanation I got once why not to do
>> this.
>
>I can't find now changes of initialization static variables, but i have
>deleted section
>dealing up with gcc warning from patch, it would go on a queue later.

Sorry, I misread the diff. That are static functions with the variables in 
them, not static structs.

Your patch to arch/sparc64/kernel/ebus.c is broken, the removed and added 
parts do not match in behaviour.

If you add braces after if's please add the '{' in the same line as the if 
itself. This will make the diff bigger, but then this matches 
Documentation/Coding-style.

Eike

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-19 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  0:25 [PATCH] pci_find_device --> pci_get_device Jiri Slaby
2005-07-19  4:36 ` Rogier Wolff
2005-07-19 10:53   ` Jiri Slaby
2005-07-19 11:15     ` Rogier Wolff
2005-07-19 11:27 ` Rolf Eike Beer
2005-07-19 15:44   ` Jiri Slaby
2005-07-19 16:20     ` Rolf Eike Beer [this message]
2005-07-20 10:40       ` Jiri Slaby
2005-07-20 11:19         ` Rolf Eike Beer
2005-07-20 12:05           ` Jiri Slaby
2005-07-20 13:56             ` Rolf Eike Beer
2005-07-20 14:40               ` Jiri Slaby

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=200507191820.35472@bilbo.math.uni-mannheim.de \
    --to=eike-kernel@sf-tec.de \
    --cc=Lionel.Bouton@inet6.fr \
    --cc=R.E.Wolff@bitwizard.nl \
    --cc=andrea@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=campbell@torque.net \
    --cc=chirag.kantharia@hp.com \
    --cc=cjtsai@ali.com.tw \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=jirislaby@gmail.com \
    --cc=kumar.gala@freescale.com \
    --cc=laredo@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@advansys.com \
    --cc=mchehab@brturbo.com.br \
    --cc=mhw@wittsend.com \
    --cc=middelin@polyware.nl \
    --cc=mulix@mulix.org \
    --cc=nils@kernelconcepts.de \
    --cc=philb@gnu.org \
    --cc=rbultje@ronald.bitfreak.net \
    --cc=rth@twiddle.net \
    --cc=support@comtrol.com \
    --cc=tim@cyberelk.net \
    /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.