From: "David S. Miller" <davem@davemloft.net>
To: bunk@stusta.de
Cc: akpm@osdl.org, nkiesel@tbdnetworks.com, acme@conectiva.com.br,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [2.6 patch] net: drop duplicate assignment in request_sock
Date: Sun, 26 Mar 2006 17:39:18 -0800 (PST) [thread overview]
Message-ID: <20060326.173918.15234485.davem@davemloft.net> (raw)
In-Reply-To: <20060326122410.GG4053@stusta.de>
From: Adrian Bunk <bunk@stusta.de>
Date: Sun, 26 Mar 2006 14:24:10 +0200
> From: Norbert Kiesel <nkiesel@tbdnetworks.com>
>
> Just noticed that request_sock.[ch] contain a useless assignment of
> rskq_accept_head to itself. I assume this is a typo and the 2nd one
> was supposed to be _tail. However, setting _tail to NULL is not
> needed, so the patch below just drops the 2nd assignment.
>
> Signed-Off-By: Norbert Kiesel <nkiesel@tbdnetworks.com>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Applied, thanks.
prev parent reply other threads:[~2006-03-27 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 12:24 [2.6 patch] net: drop duplicate assignment in request_sock Adrian Bunk
2006-03-27 1:39 ` David S. Miller [this message]
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=20060326.173918.15234485.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@conectiva.com.br \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nkiesel@tbdnetworks.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).