From: Greg KH <greg@kroah.com>
To: Hannes Reinecke <hare@suse.de>
Cc: hotplug <linux-hotplug-devel@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NULL arg for get_device() / put_device()
Date: Wed, 29 Sep 2004 16:27:48 -0700 [thread overview]
Message-ID: <20040929232748.GD26548@kroah.com> (raw)
In-Reply-To: <41590CB9.8060405@suse.de>
On Tue, Sep 28, 2004 at 09:03:21AM +0200, Hannes Reinecke wrote:
> Greg KH wrote:
> >On Mon, Sep 27, 2004 at 02:21:49PM +0200, Hannes Reinecke wrote:
> >
> >>Hi all,
> >>
> >>is there a specific reason that get_device accepts NULL as argument,
> >>whereas put_device() does not?
> >
> >
> >Um, I guess I never thought about it :)
> >
> >I don't see why it wouldn't take it, feel free to send a patch.
> >
> Here it is. Please apply.
Applied, thanks.
greg k-h
prev parent reply other threads:[~2004-09-29 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <415805DD.4040708@suse.de>
[not found] ` <20040928012801.GA11125@kroah.com>
2004-09-28 7:03 ` [PATCH] NULL arg for get_device() / put_device() Hannes Reinecke
2004-09-29 23:27 ` Greg KH [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=20040929232748.GD26548@kroah.com \
--to=greg@kroah.com \
--cc=hare@suse.de \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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