| To: | Jim Keniston <jkenisto@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6.1] Net device error logging |
| From: | Andrew Morton <akpm@xxxxxxxx> |
| Date: | Mon, 19 Jan 2004 18:46:30 -0800 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, jgarzik@xxxxxxxxx, jkenisto@xxxxxxxxxx, scott.feldman@xxxxxxxxx, kessler@xxxxxxxxxx |
| In-reply-to: | <400C3D3E.BFCC25CE@us.ibm.com> |
| References: | <400C3D3E.BFCC25CE@us.ibm.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Jim Keniston <jkenisto@xxxxxxxxxx> wrote: > > The enclosed patch implements the netdev_* error-logging macros for > network drivers. 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 logging code will be implemented mainly in terms of the `struct device'? So netdev_printk() will be a bit of netdev-specific boilerplate which then calls into a more generic device_printk()? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] IPV6: add missing sentinel for addrconf procfs, YOSHIFUJI Hideaki / 吉藤英明 |
|---|---|
| Next by Date: | Re: [Forcedeth] Wake-on-LAN support?, Carl-Daniel Hailfinger |
| Previous by Thread: | [PATCH 2.6.1] Net device error logging, Jim Keniston |
| Next by Thread: | Re: [PATCH 2.6.1] Net device error logging, Jim Keniston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |