From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Dan Carpenter <error27@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Octavian Purdila <opurdila@ixiacom.com>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] llc: cleanup: remove dead code from llc_init()
Date: Wed, 24 Mar 2010 13:54:18 +0000 [thread overview]
Message-ID: <20100324135418.GD23594@ghostprotocols.net> (raw)
In-Reply-To: <20100324115510.GC21571@bicker>
Em Wed, Mar 24, 2010 at 02:55:10PM +0300, Dan Carpenter escreveu:
> We don't need "dev" any more after:
> a5a04819c5740cb1aa217af2cc8f5ef26f33d744
> [LLC]: station source mac address
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Old leftovers, well spotted, Dave, please apply.
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
next prev parent reply other threads:[~2010-03-24 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 11:55 [patch] llc: cleanup: remove dead code from llc_init() Dan Carpenter
2010-03-24 13:54 ` Arnaldo Carvalho de Melo [this message]
2010-03-24 20:34 ` David Miller
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=20100324135418.GD23594@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=davem@davemloft.net \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/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).