mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/1] PCI: automatically set device_driver.owner
Date: Fri, 4 Nov 2005 14:55:19 -0800	[thread overview]
Message-ID: <20051104145519.3e4be1e7@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <436BDCCE.2070906@free.fr>

On Fri, 04 Nov 2005 23:12:30 +0100
Laurent Riffard <laurent.riffard@free.fr> wrote:

> 
> Le 28.10.2005 01:17, Stephen Hemminger a écrit :
> > On Thu, 27 Oct 2005 23:12:54 +0200
> > Laurent riffard <laurent.riffard@free.fr> wrote:
> > 
> > 
> >>A nice feature of sysfs is that it can create the symlink from the
> >>driver to the module that is contained in it.
> >>
> >>It requires that the device_driver.owner is set, what is not the
> >>case for many PCI drivers.
> >>
> >>This patch allows pci_register_driver to set automatically the
> >>device_driver.owner for any PCI driver.
> >>
> >>Credits to Al Viro who suggested the method.
> >>
> >>Signed-off-by: Laurent Riffard <laurent.riffard@free.fr>
> >>--
> > 
> > 
> > Okay, but a little too much macro trickery for my taste.
> 
> It was not clear to me what happened to this patch. Is it rejected?
> Or is it accepted as is? Or is a better version waited?
> 
> So here is a new version using inline functions instead of macros.

Thats better.

-- 
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger

      reply	other threads:[~2005-11-04 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 21:12 Laurent riffard
2005-10-27 23:17 ` Stephen Hemminger
2005-10-28  0:57   ` Greg KH
2005-11-04 22:12   ` Laurent Riffard
2005-11-04 22:55     ` Stephen Hemminger [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=20051104145519.3e4be1e7@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=laurent.riffard@free.fr \
    --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

all inboxes | Powered by JetHome®