Paulius Zaleckas wrote:
-/* get digits lenght, skiping blank spaces. */
+/* get digits length, skiping blank spaces. */
skiping - skipping
I haven't checked any of the other hunks for further spelling errors;
please have a look at them.
--
Stefan Richter
-=-=-=== =-== ---=-
http
mentation of the tool also contains a partial
description of the EEPROM contents.
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
Torsten Kaiser wrote:
> On 11/2/07, Stefan Richter <[EMAIL PROTECTED]> wrote:
>> To which extent do you need IEEE 1394 drivers?
>
> Using eth1394 as primary network connection on this computer.
> So switching to the new stack is currently not an option,
That's right.
: Torsten Kaiser <[EMAIL PROTECTED]>
References : http://lkml.org/lkml/2007/11/2/240
Handled-By : Jens Axboe <[EMAIL PROTECTED]>
Stefan Richter <[EMAIL PROTECTED]>
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe fr
[EMAIL PROTECTED]
References : http://lkml.org/lkml/2007/11/2/240
Handled-By : Jens Axboe [EMAIL PROTECTED]
Stefan Richter [EMAIL PROTECTED]
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux
Torsten Kaiser wrote:
On 11/2/07, Stefan Richter [EMAIL PROTECTED] wrote:
To which extent do you need IEEE 1394 drivers?
Using eth1394 as primary network connection on this computer.
So switching to the new stack is currently not an option,
That's right.
Looking that calltrace upwards
). The documentation of the tool also contains a partial
description of the EEPROM contents.
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
t;> 51 sg->page_link = page_link | (unsigned long) page;
>> 52 }
>> 53
>
> Uh oh...
>
> I'm afraid the ieee1394 core's own scatter-gather list managing code
> didn't survive the changes in the kernel's s/g list implementation.
>
> Alas I will
ll be quite busy with non-Linux related stuff during at least
the next two weeks and can't fix this myself for now.
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
fix this myself for now.
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
.
Jens, maybe you can come up with a fix quicker than I could.
--
Stefan Richter
-=-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
Nick Piggin wrote:
> On Thursday 01 November 2007 12:49, Stefan Richter wrote:
>> fw_device.node_id and fw_device.generation are accessed without mutexes.
>> We have to ensure that all readers will get to see node_id updates
>> before generation updates.
>>
>
roduction and trains
users to lower their expectations.
--
Stefan Richter
-=-=-=== =-== =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/maj
.
--
Stefan Richter
-=-=-=== =-== =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Nick Piggin wrote:
On Thursday 01 November 2007 12:49, Stefan Richter wrote:
fw_device.node_id and fw_device.generation are accessed without mutexes.
We have to ensure that all readers will get to see node_id updates
before generation updates.
Hi, a few points:
Thanks, this is appreciated
reading.
We now restart reading the ROM if the bus generation changed.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-device.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
Index: linux/drivers/firewire/fw-de
-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-sbp2.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
Index: linux/drivers/firewire/fw-sbp2.c
===
--- linux.orig/drivers/firewire/fw-sbp2.c
+++
fw_device.node_id and fw_device.generation are accessed without mutexes.
We have to ensure that all readers will get to see node_id updates
before generation updates.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-device.c |6 ++
drivers/firew
potted by the Intel C Compiler.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
diff --git a/drivers/ieee1394/ieee1394_transactions.c
b/drivers/ieee1394/ieee1394_transactions.c
index c39c70a..6779893 100644
---
Cornelia Huck wrote:
> On Wed, 31 Oct 2007 10:52:35 +0100,
> Stefan Richter <[EMAIL PROTECTED]> wrote:
>> if (!grp->is_visible ||
>> grp->is_visible(kobj, *attr, i))
>> add or remove();
>>
he meaning of the callback
> around?
>
> for (...) {
> if (grp->mask_out && grp->mask_out(kobj, *attr, i))
> continue;
> error |= sysfs_add_file(...);
> }
if (!grp->is_visible ||
grp->is_visi
))
continue;
error |= sysfs_add_file(...);
}
if (!grp-is_visible ||
grp-is_visible(kobj, *attr, i))
add or remove();
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line
Cornelia Huck wrote:
On Wed, 31 Oct 2007 10:52:35 +0100,
Stefan Richter [EMAIL PROTECTED] wrote:
if (!grp-is_visible ||
grp-is_visible(kobj, *attr, i))
add or remove();
Hm, I find that a bit harder to parse...
if (grp
by the Intel C Compiler.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
diff --git a/drivers/ieee1394/ieee1394_transactions.c
b/drivers/ieee1394/ieee1394_transactions.c
index c39c70a..6779893 100644
--- a/drivers/ieee1394/ieee1394_transactions.c
fw_device.node_id and fw_device.generation are accessed without mutexes.
We have to ensure that all readers will get to see node_id updates
before generation updates.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-device.c |6 ++
drivers/firewire/fw-topology.c
reading.
We now restart reading the ROM if the bus generation changed.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-device.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
Index: linux/drivers/firewire/fw-device.c
-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-sbp2.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
Index: linux/drivers/firewire/fw-sbp2.c
===
--- linux.orig/drivers/firewire/fw-sbp2.c
+++ linux
James Bottomley wrote:
> OK, so is this latest revision acceptable to everyone?
No complaint from me. (I'm more or less by accident in this thread
anyway. Once this feature is available in mainline, I may have use for
it in drivers/firewire/ though.) Thanks,
--
Stefan Rich
James Bottomley wrote:
OK, so is this latest revision acceptable to everyone?
No complaint from me. (I'm more or less by accident in this thread
anyway. Once this feature is available in mainline, I may have use for
it in drivers/firewire/ though.) Thanks,
--
Stefan Richter
ed.
How about this:
int (*is_visible)(...);
or
bool (*shall_be_shown)(...);
or
bool (*should_be_displayed)(...);
or whatever, so that it indicates that this function merely answers a
question, but doesn't filter nor show anything.
--
Stefan Richter
-=-=-===
(*is_visible)(...);
or
bool (*shall_be_shown)(...);
or
bool (*should_be_displayed)(...);
or whatever, so that it indicates that this function merely answers a
question, but doesn't filter nor show anything.
--
Stefan Richter
-=-=-=== =-=- ===-=
http://arcgraph.de/sr/
-
To unsubscribe
Krzysztof Halasa wrote:
> Stefan Richter <[EMAIL PROTECTED]> writes:
>> # ./a.out 00:0a.3
>> I/O region #1 is at C800
>> It seems your VT6307 chip is connected to 93c46 EEPROM
>
> Interesting, really. Perhaps they aimed at I2C too with 9306 but
>
at virtual address 0xb7f2f004
EEPROM dump:
00: 00 11 06 00 00 00 41 CC 04 04 32 55 F8 00 92 02
10: A1 00 40 63 06 11 44 30 03 DF 40 80 00 20 00 73
20: 3C 10 00 00 00 00 A0 00 FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.0 mode
> and, if you tri
Adrian Bunk wrote:
> This patch removes dead code spotted by the Intel C Compiler.
Committed to linux1394-2.6.git, thanks.
--
Stefan Richter
-=-=-=== =-=- ===--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
Tilman Schmidt wrote:
> Am 28.10.2007 10:25 schrieb Stefan Richter:
>> You two are hypothesizing.
>
> No, we're not. We're discussing the very real issue of whether
> LSM should be amputated in such a way as to make life difficult
> for out of tree security module developers.
anges into mainline, IOW to take
part in the Linux kernel project.
²) Of course if such projects chose to become part of the Linux kernel
project, they would get to enjoy additional bonuses as outlined at the
end of stable_api_nonsense.txt. Sure, becoming part of the project
involves to coop
if such projects chose to become part of the Linux kernel
project, they would get to enjoy additional bonuses as outlined at the
end of stable_api_nonsense.txt. Sure, becoming part of the project
involves to cooperate, and not everybody wants or can afford to do so.
--
Stefan Richter
Tilman Schmidt wrote:
Am 28.10.2007 10:25 schrieb Stefan Richter:
You two are hypothesizing.
No, we're not. We're discussing the very real issue of whether
LSM should be amputated in such a way as to make life difficult
for out of tree security module developers.
I still believe you
Adrian Bunk wrote:
This patch removes dead code spotted by the Intel C Compiler.
Committed to linux1394-2.6.git, thanks.
--
Stefan Richter
-=-=-=== =-=- ===--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
F8 00 92 02
10: A1 00 40 63 06 11 44 30 03 DF 40 80 00 20 00 73
20: 3C 10 00 00 00 00 A0 00 FF FF FF FF FF FF FF FF
Your VT6307 chip is in OHCI 1.0 mode
and, if you tried upgrading or downgrading, if it worked.
I haven't tried it yet.
--
Stefan Richter
Krzysztof Halasa wrote:
Stefan Richter [EMAIL PROTECTED] writes:
# ./a.out 00:0a.3
I/O region #1 is at C800
It seems your VT6307 chip is connected to 93c46 EEPROM
Interesting, really. Perhaps they aimed at I2C too with 9306 but
screwed up the silicon? Would have to look
Tilman Schmidt wrote about:
> breaking interfaces they rely on for no other "very good
> reason" than to discourage out-of-tree development?
How often did this happen yet?
--
Stefan Richter
-=-=-=== =-=- ==-==
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the l
Tilman Schmidt wrote about:
breaking interfaces they rely on for no other very good
reason than to discourage out-of-tree development?
How often did this happen yet?
--
Stefan Richter
-=-=-=== =-=- ==-==
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe
changed, 9 insertions(+), 4 deletions(-)
Stefan Richter (2):
firewire: fw-ohci: log a note about unsupported features
firewire: fw-ohci: shut up a superfluous compiler warning
Full log and diff:
commit 4b6d51ec62d9c57432430528d6293605794a9f1b
Author: Stefan Richter <[EMAIL PROTEC
changed, 9 insertions(+), 4 deletions(-)
Stefan Richter (2):
firewire: fw-ohci: log a note about unsupported features
firewire: fw-ohci: shut up a superfluous compiler warning
Full log and diff:
commit 4b6d51ec62d9c57432430528d6293605794a9f1b
Author: Stefan Richter [EMAIL PROTECTED
ayload_bus is conditional on packet->payload_length > 0,
and that won't change while in at_context_queue_packet.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-ohci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/driv
is conditional on packet-payload_length 0,
and that won't change while in at_context_queue_packet.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/drivers/firewire/fw-ohci.c
oth chips are quite widespread. From what I remember to have seen,
most VT6307 are programmed in OHCI 1.1 mode while all VT6306 seem to be
OHCI 1.0.
--
Stefan Richter
-=-=-=== =-=- =-=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
ontents which state OHCI 1.0 implementation level, and just treats
these VIA chips as OHCI 1.1 implementations?
--
Stefan Richter
-=-=-=== =-=- =-=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL P
implementation level, and just treats
these VIA chips as OHCI 1.1 implementations?
--
Stefan Richter
-=-=-=== =-=- =-=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
are quite widespread. From what I remember to have seen,
most VT6307 are programmed in OHCI 1.1 mode while all VT6306 seem to be
OHCI 1.0.
--
Stefan Richter
-=-=-=== =-=- =-=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Krzysztof Halasa wrote:
> Is the "dual buffer reception" involved in receiving video from
> a DV camera, using the new driver?
Yes, isochronous reception (and thus DV) with the new drivers currently
requires dual buffer mode.
--
Stefan Richter
-=-=-=== =-=- =---=
http:
Krzysztof Halasa wrote:
> Stefan Richter <[EMAIL PROTECTED]> writes:
>
>> And in case of VT6307, I suspect it's VIA who
>> selects the implementation level (based on chip revision), not the card
>> vendor.
>
> Can't be, the customers (real ones - boa
g that could be common in the best case is the symlink to
the partition's device file, based on filesystem UUID or filesystem label.
¹) unless you write your own rule specific to this on particular enclosure
--
Stefan Richter
-=-=-=== =-=- =---=
http://arcgraph.de/sr/
-
To unsubscribe fro
is the symlink to
the partition's device file, based on filesystem UUID or filesystem label.
¹) unless you write your own rule specific to this on particular enclosure
--
Stefan Richter
-=-=-=== =-=- =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
Krzysztof Halasa wrote:
Stefan Richter [EMAIL PROTECTED] writes:
And in case of VT6307, I suspect it's VIA who
selects the implementation level (based on chip revision), not the card
vendor.
Can't be, the customers (real ones - board makers) would kill them
at once and then buy
Krzysztof Halasa wrote:
Is the dual buffer reception involved in receiving video from
a DV camera, using the new driver?
Yes, isochronous reception (and thus DV) with the new drivers currently
requires dual buffer mode.
--
Stefan Richter
-=-=-=== =-=- =---=
http://arcgraph.de/sr
Kaehlcke (1):
ieee1394: ieee1394_core.c: use DEFINE_SPINLOCK for spinlock definition
Satyam Sharma (1):
ieee1394: Fix kthread stopping in nodemgr_host_thread
Stefan Richter (20):
ieee1394: eth1394: superfluous local variable
ieee1394: eth1394: fix lock imbalance
ieee1394
s; i.e. this
documentation can't be trusted to begin with.
As far as VT6306 is concerned, the wording could be copy'n'waste from
the VT6307 datasheet. And in case of VT6307, I suspect it's VIA who
selects the implementation level (based on chip revision), not the card
vendor.
--
Stefan R
speaking default
names for device files, just like we already provide speaking default
names for network interfaces. (Not for all, but for many.)
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
CSI namespace and then this namespace
is divided again, it's not a big issue anymore whether PATA and SATA
share an ATA namespace or are distinct, except perhaps for people with
IDE drive and eSATA slots.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from thi
I wrote:
> The CPU must not touch the buffer after it was DMA-mapped.
>
> Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
> ---
> drivers/firewire/fw-ohci.c |1 +
> 1 file changed, 1 insertion(+)
>
> Index: li
All of the buffers which are allocated during fw-ohci's pci_probe can be
allocated with GFP_KERNEL.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-ohci.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
Index: linux-2.6.23-rc6/drivers/firew
Sync only the parts for CPU which are actually accessed by the CPU.
Replace a memset by direct assignment.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-ohci.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
Index: linux/d
The CPU must not touch the buffer after it was DMA-mapped.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-ohci.c |1 +
1 file changed, 1 insertion(+)
Index: linux/drivers/firewire/fw-
rection
follows in a minute.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the F
The CPU must not touch the buffer after it was DMA-mapped.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
drivers/firewire/fw-ohci.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
Index: linux/drivers/firewire/fw-
e use of the new naming functions in
lib/, providing either just "sd", "sr" etc. or "sd-$transport-" as
name prefix
No patch yet, and alas I'm currently short of spare time.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscrib
. or sd-$transport- as
name prefix
No patch yet, and alas I'm currently short of spare time.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
The CPU must not touch the buffer after it was DMA-mapped.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
Index: linux/drivers/firewire/fw-ohci.c
.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The CPU must not touch the buffer after it was DMA-mapped.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c |1 +
1 file changed, 1 insertion(+)
Index: linux/drivers/firewire/fw-ohci.c
Sync only the parts for CPU which are actually accessed by the CPU.
Replace a memset by direct assignment.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
Index: linux/drivers
All of the buffers which are allocated during fw-ohci's pci_probe can be
allocated with GFP_KERNEL.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
Index: linux-2.6.23-rc6/drivers/firewire/fw
I wrote:
The CPU must not touch the buffer after it was DMA-mapped.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
---
drivers/firewire/fw-ohci.c |1 +
1 file changed, 1 insertion(+)
Index: linux/drivers/firewire/fw-ohci.c
whether PATA and SATA
share an ATA namespace or are distinct, except perhaps for people with
IDE drive and eSATA slots.
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
default
names for device files, just like we already provide speaking default
names for network interfaces. (Not for all, but for many.)
--
Stefan Richter
-=-=-=== =-=- =
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
. this
documentation can't be trusted to begin with.
As far as VT6306 is concerned, the wording could be copy'n'waste from
the VT6307 datasheet. And in case of VT6307, I suspect it's VIA who
selects the implementation level (based on chip revision), not the card
vendor.
--
Stefan Richter
Kaehlcke (1):
ieee1394: ieee1394_core.c: use DEFINE_SPINLOCK for spinlock definition
Satyam Sharma (1):
ieee1394: Fix kthread stopping in nodemgr_host_thread
Stefan Richter (20):
ieee1394: eth1394: superfluous local variable
ieee1394: eth1394: fix lock imbalance
ieee1394
[EMAIL PROTECTED] wrote:
> On Mon, 15 Oct 2007, Stefan Richter wrote:
>> Low-level networking drivers suggest a default interface name (per
>> interface or as a template like eth%d into which the networking core
>> inserts a lowest spare number).
...
>> Could low-level S
reWire tape drive,
/dev/sda- a device whose transport driver didn't propose a name
Of course the really interesting names will still be provided by
udev-generated symlinks.
--
Stefan Richter
-=-=-=== =-=- -
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "uns
interesting names will still be provided by
udev-generated symlinks.
--
Stefan Richter
-=-=-=== =-=- -
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
[EMAIL PROTECTED] wrote:
On Mon, 15 Oct 2007, Stefan Richter wrote:
Low-level networking drivers suggest a default interface name (per
interface or as a template like eth%d into which the networking core
inserts a lowest spare number).
...
Could low-level SCSI drivers provide similar name
SCSI transport protocol, hence ieee1394/sbp2
and firewire/fw-sbp2 are Linux SCSI low-level drivers. Anything else
would be just wrong and infeasible in this particular case.
--
Stefan Richter
-=-=-=== =-=- -
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line &
;packets);
> end = (void __user *)p + request->size;
> count = 0;
> while (p < end) {
Acked-by: Stefan Richter <[EMAIL PROTECTED]>
I will enqueue it in case Linus doesn't pick it up before my next pull
request.
--
Stefan Richter
-=-=-=== =-=- -===-
http://arc
out for a fight rather than
interested in help.
--
Stefan Richter
-=-=-=== =-=- -===-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majord
for a fight rather than
interested in help.
--
Stefan Richter
-=-=-=== =-=- -===-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
;
while (p end) {
Acked-by: Stefan Richter [EMAIL PROTECTED]
I will enqueue it in case Linus doesn't pick it up before my next pull
request.
--
Stefan Richter
-=-=-=== =-=- -===-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
ieee1394/sbp2
and firewire/fw-sbp2 are Linux SCSI low-level drivers. Anything else
would be just wrong and infeasible in this particular case.
--
Stefan Richter
-=-=-=== =-=- -
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Jan Engelhardt wrote:
> On Oct 13 2007 10:16, Stefan Richter wrote:
>> Perhaps say
>>
>> warning("override: switching to choice %s", sym->name);
>>
>> if sym->name is [CONFIG_]PREEMPT_VOLUNTARY. Or what is it?
>
> .config:176:war
PT_NONE is not set
> CONFIG_REEMPT_VOLUNTARY=y
Perhaps say
warning("override: switching to choice %s", sym->name);
if sym->name is [CONFIG_]PREEMPT_VOLUNTARY. Or what is it?
--
Stefan Richter
-=-=-=== =-=- -==-=
http://arcgraph.de/sr/
-
To unsubscribe from this li
-name);
if sym-name is [CONFIG_]PREEMPT_VOLUNTARY. Or what is it?
--
Stefan Richter
-=-=-=== =-=- -==-=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
Jan Engelhardt wrote:
On Oct 13 2007 10:16, Stefan Richter wrote:
Perhaps say
warning(override: switching to choice %s, sym-name);
if sym-name is [CONFIG_]PREEMPT_VOLUNTARY. Or what is it?
.config:176:warning: override: reassigning to symbol PREEMPT_VOLUNTARY
.config:176:warning
Matthias Kaehlcke wrote:
> drivers/ieee1394/ieee1394_core.c: Define spinlock using
> DEFINE_SPINLOCK instead of assignment to SPIN_LOCK_UNLOCKED
Committed to linux1394-2.6.git, thanks.
--
Stefan Richter
-=-=-=== =-=- -==--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send th
Matthias Kaehlcke wrote:
drivers/ieee1394/ieee1394_core.c: Define spinlock using
DEFINE_SPINLOCK instead of assignment to SPIN_LOCK_UNLOCKED
Committed to linux1394-2.6.git, thanks.
--
Stefan Richter
-=-=-=== =-=- -==--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line
Trond Myklebust wrote:
> On Thu, 2007-10-11 at 23:21 +0200, Stefan Richter wrote:
>> people in the patch
>> forwarding chain should only add this tag if the reviewer sent it
>> explicitly in his response. Unlike with Acked-by and Tested-by, we must
>> not guess wheth
r function properly in any
>> + given situation.
>
> I'm confused about how to reconcile (c) and (d) here. If you are not
> sure about whether or not the patch will achieve its stated purpose, why
> would you be arguing that it is a worthwhile modific
) here. If you are not
sure about whether or not the patch will achieve its stated purpose, why
would you be arguing that it is a worthwhile modification?
Being sure of something and making guarantees are different things.
--
Stefan Richter
-=-=-=== =-=- -=-==
http://arcgraph.de/sr
Trond Myklebust wrote:
On Thu, 2007-10-11 at 23:21 +0200, Stefan Richter wrote:
people in the patch
forwarding chain should only add this tag if the reviewer sent it
explicitly in his response. Unlike with Acked-by and Tested-by, we must
not guess whether a reviewer wants to have his
Fix panic in run_timer_softirq right after "modprobe -r firewire-ohci"
if a FireWire disk was attached and firewire-sbp2 loaded.
Same as commit 8a2d9ed3210464d22fccb9834970629c1c36fa36.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
(I somehow forgot to send this ear
801 - 900 of 2238 matches
Mail list logo
