From: Frank Haverkamp <haver@linux.vnet.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de,
cody@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
utz.bacher@de.ibm.com, mmarek@suse.cz, rmallon@gmail.com,
jsvogt@de.ibm.com, MIJUNG@de.ibm.com,
cascardo@linux.vnet.ibm.com, michael@ibmra.de,
Frank Haverkamp <haver@vnet.ibm.com>
Subject: Re: [PATCH] Generic WorkQueue Engine (GenWQE) device driver (v4)
Date: Tue, 05 Nov 2013 08:16:24 +0100 [thread overview]
Message-ID: <1383635784.11383.2.camel@oc7383187364.ibm.com> (raw)
In-Reply-To: <20131104221524.GD14141@kroah.com>
Hi Greg,
Am Montag, den 04.11.2013, 14:15 -0800 schrieb Greg KH:
> > I am using sysfs_create_group() now, but do I understand you
> correctly
> > that setting the const struct attribute_group **groups; in my device
> > (where in my struct pci_device.dev?) is an even better way to
> establish
> > my sysfs attributes? Is there a function which I could call rather
> than
> > trying to find the right pointer?
>
> Ugh, this is still a problem, I'm trying to work through how to have
> individual drivers implement groups and sysfs files in a non-racy way.
> The issue is your device was announced to userspace _before_ it was
> bound to the driver, so there's no way to get the sysfs files to apply
> before then.
>
> You should just have the attributes on the sysfs device you create
> yourself, not your pci device, as that's where they make more sense,
> and
> there you should be able to use the attribute group easily, right?
>
The current version works well for me and I did not get any complaints
about the possible race-condition you mentioned so far. So I am happy.
> thanks,
>
> greg k-h
Greetings
Frank
next prev parent reply other threads:[~2013-11-05 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 9:32 Frank Haverkamp
2013-10-30 9:32 ` Frank Haverkamp
2013-10-30 17:35 ` Greg KH
2013-10-30 20:38 ` Ryan Mallon
2013-11-04 16:19 ` Frank Haverkamp
2013-11-04 16:18 ` Frank Haverkamp
2013-10-30 17:36 ` Greg KH
2013-11-04 16:20 ` Frank Haverkamp
2013-10-30 17:37 ` Greg KH
2013-11-04 16:30 ` Frank Haverkamp
2013-10-30 17:39 ` Greg KH
2013-10-30 17:44 ` Greg KH
2013-11-04 16:41 ` Frank Haverkamp
2013-11-04 22:15 ` Greg KH
2013-11-05 7:16 ` Frank Haverkamp [this message]
2013-11-05 12:50 ` Greg KH
2013-10-31 3:49 ` Ryan Mallon
2013-11-04 16:44 ` Frank Haverkamp
2013-11-04 16:45 ` Frank Haverkamp
2013-11-12 13:50 ` Pavel Machek
2013-11-13 12:36 ` Frank Haverkamp
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=1383635784.11383.2.camel@oc7383187364.ibm.com \
--to=haver@linux.vnet.ibm.com \
--cc=MIJUNG@de.ibm.com \
--cc=arnd@arndb.de \
--cc=cascardo@linux.vnet.ibm.com \
--cc=cody@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=haver@vnet.ibm.com \
--cc=jsvogt@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ibmra.de \
--cc=mmarek@suse.cz \
--cc=rmallon@gmail.com \
--cc=schwidefsky@de.ibm.com \
--cc=utz.bacher@de.ibm.com \
/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®