From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Advice on first patch
Date: Tue, 02 Oct 2012 13:29:14 +0200 [thread overview]
Message-ID: <87pq51m7sl.fsf@nemi.mork.no> (raw)
In-Reply-To: <1349175364-21936-1-git-send-email-matthew@walster.org> (matthew@walster.org's message of "Tue, 2 Oct 2012 11:56:03 +0100")
matthew at walster.org writes:
> I'm hopefully going to be submitting the attached patch to the
> mainline kernel tree, and as it's my first patch, I figured it would
> be wise to run it past KN first in case I'd done something
> monumentally stupid! I found it through a checkpatch run, from the
> excellent talk by GregKH at FOSDEM a year or so back.
>
> Any input would be greatly appreciated!
Looks fine to me, but you might want to remove/update the related
comment as well:
/*
* This ALLMULTI check should be redundant by 1.4
* so don't forget to remove it.
*
* Seems, you forgot to remove it. All silly devices
* seems to set IFF_PROMISC.
*/
else if (1 /*dev->flags&IFF_PROMISC */ ) {
if (unlikely(!ether_addr_equal_64bits(eth->h_dest,
dev->dev_addr)))
skb->pkt_type = PACKET_OTHERHOST;
}
Looks like someone was expecting a 1.4 at the time. We know better now
:-)
Bj?rn
next prev parent reply other threads:[~2012-10-02 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 10:56 Advice on first patch matthew at walster.org
2012-10-02 10:56 ` [PATCH] net: ethernet: clean out braces / old code (found via checkpatch) matthew at walster.org
2012-10-02 16:16 ` Scott Lovenberg
2012-10-03 9:13 ` Matthew Walster
2012-10-03 13:12 ` Scott Lovenberg
2012-10-04 16:13 ` Matthew Walster
2012-10-04 18:54 ` Bjørn Mork
2012-10-02 11:29 ` Bjørn Mork [this message]
2012-10-02 11:34 ` Advice on first patch Matthew Walster
2012-10-03 9:25 ` Bjørn Mork
2012-10-03 13:40 ` Peter Senna Tschudin
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=87pq51m7sl.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).