patch acceptance question

patch acceptance question

[Don Fry]

I was surprised today to see a change to pcnet32.c in 2.6.31-rc2-git4
which maybe I missed yesterday on netdev.  Most of the changes are okay,
but one in particular will result in some ugly printing.

What is the path that (probably janitorial) changes take that get
included in mainline?   Had I seen it before it went in I would have
commented on it then.

Old:
pcnet32: PCnet/FAST+ 79C972 at 0x1020, 00:0c:46:53:8d:0c
    tx_start_pt(0x0c00):~220 bytes, BCR18(9861):BurstWrEn BurstRdEn
NoUFlow 
    SRAMSIZE=0x1700, SRAM_BND=0x0800, assigned IRQ 21.


New:
pcnet32: PCnet/FAST+ 79C972 at 0x1020, 00:0c:46:53:8d:0c<6>  tx_start_pt
(0x0c00):~220 bytes, BCR18(9861):BurstWrEn BurstRdEn NoUFlow 
    SRAMSIZE=0x1700, SRAM_BND=0x0800, assigned IRQ 21.


Thanks,
Don Fry

Re: patch acceptance question

[David Miller]

From: Don Fry <pcnet32@verizon.net>
Date: Thu, 09 Jul 2009 08:21:36 -0700

> I was surprised today to see a change to pcnet32.c in 2.6.31-rc2-git4
> which maybe I missed yesterday on netdev.  Most of the changes are okay,
> but one in particular will result in some ugly printing.
> 
> What is the path that (probably janitorial) changes take that get
> included in mainline?   Had I seen it before it went in I would have
> commented on it then.

In the amount of typing you did for sending this email, you
could have submitted a fix instead.

I think the change in question went straight into Linus's tree.