From: Jeff Garzik <jeff@garzik.org>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] dm9601: Fix multicast hash table handling
Date: Tue, 25 Mar 2008 23:33:45 -0400 [thread overview]
Message-ID: <47E9C419.3040706@garzik.org> (raw)
In-Reply-To: <47E9C0E3.6040404@garzik.org>
Jeff Garzik wrote:
> Peter Korsgaard wrote:
>> The loop forgot to walk the net->mc_list list, so only the first
>> multicast address was programmed into the hash table.
>>
>> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
>> ---
>> drivers/net/usb/dm9601.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> applied three patches.
>
> Please number your patches in the future, to indicate the order of
> application -- even if they are roughly independent, it helps to know
> they are in the same patch series by some method other than just the
> References RFC-822 header
I take that back... this breaks the build: 'mlist' not defined
next prev parent reply other threads:[~2008-03-26 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 22:16 [PATCH] dm9601: Fix multicast hash table handling Peter Korsgaard
2008-03-18 22:16 ` [PATCH] dm9601: add Hirose USB-100 device ID Peter Korsgaard
2008-03-18 22:16 ` [PATCH] dm9601: configure MAC to drop invalid (crc/length) packets Peter Korsgaard
2008-03-26 3:20 ` [PATCH] dm9601: Fix multicast hash table handling Jeff Garzik
2008-03-26 3:33 ` Jeff Garzik [this message]
2008-03-26 7:51 ` Peter Korsgaard
2008-03-26 7:34 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2008-03-28 21:25 Peter Korsgaard
2008-03-29 1:53 ` Jeff Garzik
2008-03-29 9:23 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E9C419.3040706@garzik.org \
--to=jeff@garzik.org \
--cc=jacmet@sunsite.dk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.