Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\.1\]\s+Net\s+device\s+error\s+logging\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\.1\]\s+Net\s+device\s+error\s+logging\s*$/: 10 ]

Total 10 documents matching your query.

1. [PATCH 2.6.1] Net device error logging (score: 1): Author: shemminger@xxxxxxxx>; Date: Mon, 19 Jan 2004 12:25:34 -0800; The enclosed patch implements the netdev_* error-logging macros for network drivers. These macros have been discussed at length on the linux-kernel and linux-netdev lists. All issues that reviewers h; /archives/netdev/2004-01/msg00404.html (16,736 bytes)
2. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: a <sri@xxxxxxxxxx>; Date: Mon, 19 Jan 2004 18:46:30 -0800; Looks OK to me. But it does make one wonder whether we'll soon see standalone patches for scsi_printk(), pci_bridge_printk(), random_other_subsystem_printk(), ...? Or is it intended that the backend; /archives/netdev/2004-01/msg00422.html (8,381 bytes)
3. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: S. Miller" <davem@xxxxxxxxxx>; Date: Tue, 20 Jan 2004 19:51:22 +0100; How about a message rate limit? -- Regards, Rask Ingemann Lambertsen; /archives/netdev/2004-01/msg00439.html (8,586 bytes)
4. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author:; Date: Tue, 20 Jan 2004 15:06:21 -0800; Thanks. We considered adding a ratelimit flag to the netdev_printk arg list. It was pointed out that (1) rate-limiting is necessary for a relatively small subset of messages; and (2) the NETIF_MSG_*; /archives/netdev/2004-01/msg00443.html (8,971 bytes)
5. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: xxxx>; Date: Tue, 20 Jan 2004 15:19:29 -0800; Well, there is indeed sdev_printk for the SCSI mid-layer and low-level drivers. Dan Stekloff posted an updated patch for this on linux-scsi yesterday. When Alan Cox suggested dev_printk, it was with; /archives/netdev/2004-01/msg00444.html (9,569 bytes)
6. [PATCH 2.6.1] Net device error logging (score: 1): Author: Jim Keniston <jkenisto@xxxxxxxxxx>; Date: Mon, 19 Jan 2004 12:25:34 -0800; The enclosed patch implements the netdev_* error-logging macros for network drivers. These macros have been discussed at length on the linux-kernel and linux-netdev lists. All issues that reviewers h; /archives/netdev/2004-01/msg01112.html (16,736 bytes)
7. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: Andrew Morton <akpm@xxxxxxxx>; Date: Mon, 19 Jan 2004 18:46:30 -0800; Looks OK to me. But it does make one wonder whether we'll soon see standalone patches for scsi_printk(), pci_bridge_printk(), random_other_subsystem_printk(), ...? Or is it intended that the backend; /archives/netdev/2004-01/msg01130.html (8,431 bytes)
8. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>; Date: Tue, 20 Jan 2004 19:51:22 +0100; How about a message rate limit? -- Regards, Rask Ingemann Lambertsen; /archives/netdev/2004-01/msg01147.html (8,680 bytes)
9. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: Jim Keniston <jkenisto@xxxxxxxxxx>; Date: Tue, 20 Jan 2004 15:06:21 -0800; Thanks. We considered adding a ratelimit flag to the netdev_printk arg list. It was pointed out that (1) rate-limiting is necessary for a relatively small subset of messages; and (2) the NETIF_MSG_*; /archives/netdev/2004-01/msg01151.html (9,024 bytes)
10. Re: [PATCH 2.6.1] Net device error logging (score: 1): Author: Jim Keniston <jkenisto@xxxxxxxxxx>; Date: Tue, 20 Jan 2004 15:19:29 -0800; Well, there is indeed sdev_printk for the SCSI mid-layer and low-level drivers. Dan Stekloff posted an updated patch for this on linux-scsi yesterday. When Alan Cox suggested dev_printk, it was with; /archives/netdev/2004-01/msg01152.html (9,630 bytes)

Current List: 1 - 10
Page: [1]