The patch titled sky2: avoid divide in receive path has been added to the -mm tree. Its filename is sky2-avoid-divide-in-receive-path.patch *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: sky2: avoid divide in receive path From: Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> Avoid divide (modulus) in receive buffer handling path. Signed-off-by: Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/net/sky2.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletion(-) diff -puN drivers/net/sky2.c~sky2-avoid-divide-in-receive-path drivers/net/sky2.c --- a/drivers/net/sky2.c~sky2-avoid-divide-in-receive-path +++ a/drivers/net/sky2.c @@ -2140,7 +2140,8 @@ static struct sk_buff *sky2_receive(stru printk(KERN_DEBUG PFX "%s: rx slot %u status 0x%x len %d\n", dev->name, sky2->rx_next, status, length); - sky2->rx_next = (sky2->rx_next + 1) % sky2->rx_pending; + if (++sky2->rx_next >= sky2->rx_pending) + sky2->rx_next = 0; prefetch(sky2->rx_ring + sky2->rx_next); if (status & GMR_FS_ANY_ERR) _ Patches currently in -mm which might be from shemminger@xxxxxxxxxxxxxxxxxxxx are origin.patch pci-x-pci-express-read-control-interfaces-mthca.patch pci-x-pci-express-read-control-interfaces-e1000.patch sky2-fe-chip-support.patch sky2-use-debugfs-rename.patch sky2-document-gphy_ctrl-bits.patch sky2-dont-restrict-config-space-access.patch sky2-advanced-error-reporting.patch sky2-use-pci_config-access-functions.patch sky2-use-net_device-internal-stats.patch ktime_sub_ns-analog-of-ktime_add_ns.patch export-reciprocal_value-for-modules.patch sky2-hardware-receive-timestamp-counter.patch sky2-avoid-divide-in-receive-path.patch sky2-118.patch git-net.patch i386-optimize-memset-of-6-and-8-bytes.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html