On 2011-10-14 16:48, Jan Kiszka wrote:
On 2011-10-06 17:48, Jesse Barnes wrote:
On Mon, 12 Sep 2011 18:54:01 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access
On Mon, Sep 12, 2011 at 06:54:01PM +0200, Jan Kiszka wrote:
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
assumes it is only called by one instance at a time for some
On 2011-10-06 17:48, Jesse Barnes wrote:
On Mon, 12 Sep 2011 18:54:01 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
On 10/06/2011 10:48 AM, Jesse Barnes wrote:
On Mon, 12 Sep 2011 18:54:01 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
On Mon, 12 Sep 2011 18:54:01 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
assumes it is only called by one instance at a
This series tries to heal the currently broken locking scheme around PCI
config space accesses.
We have an interface lock out access via sysfs, but that service wrongly
assumes it is only called by one instance at a time for some device. So
two loops doing
echo 1
