public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	linux-kernel@vger.kernel.org, rth@twiddle.net,
	dhowells@redhat.com, kumar.gala@freescale.com,
	davem@davemloft.net, mhw@wittsend.com, support@comtrol.com,
	nils@kernelconcepts.de, chirag.kantharia@hp.com,
	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,
	mulix@mulix.org
Subject: Re: [PATCH] pci_find_device --> pci_get_device
Date: Tue, 19 Jul 2005 13:15:42 +0200	[thread overview]
Message-ID: <20050719111542.GA26422@bitwizard.nl> (raw)
In-Reply-To: <42DCDBB2.6070106@gmail.com>

On Tue, Jul 19, 2005 at 12:53:38PM +0200, Jiri Slaby wrote:
> Rogier Wolff napsal(a):

> I don't know, if you think it global, or if am I here with other
> fellows (no, I'm not).  I don't know what kind of comment you have
> on your mind. Could you, please, specify it more.  I only changed
> names of called functions and added some pci_dev_put, what should I
> comment?

I meant: that IF I'm right that there needs to be more pci_dev_put, 
that needs to be noted in the source. 

If you know that there needs to be a put, but you have decided you
don't know where to put it exactly, then that needs to be in a comment
so that someone looking at the code after you will be able to put it
in. Otherwise the new person will think: He might have had a smarter
plan and will do the pci_dev_put somewhere else. 

	Roger. 


-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  reply	other threads:[~2005-07-19 11:15 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 [this message]
2005-07-19 11:27 ` Rolf Eike Beer
2005-07-19 15:44   ` Jiri Slaby
2005-07-19 16:20     ` Rolf Eike Beer
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=20050719111542.GA26422@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=Lionel.Bouton@inet6.fr \
    --cc=andrea@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=campbell@torque.net \
    --cc=chirag.kantharia@hp.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox