netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jonathan Naylor <g4klx@g4klx.demon.co.uk>,
	netdev@oss.sgi.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] net/lapb/lapb_iface.c: remove unused code
Date: Wed, 15 Dec 2004 23:58:22 +0000	[thread overview]
Message-ID: <1103155101.3585.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20041215010745.GB12937@stusta.de>

On Mer, 2004-12-15 at 01:07, Adrian Bunk wrote:
> The patch below removes the following unused code:
> - EXPORT_SYMBOL'ed functions lapb_getparms and lapb_setparms
> - struct lapb_parms_struct
> 
> Please review whether it's correct or conflicts with pending changes.

Please keep these, they are used by out of kernel code and they are also
required in order to run test sets on the full code functionality.

      reply	other threads:[~2004-12-15 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15  1:07 [2.6 patch] net/lapb/lapb_iface.c: remove unused code Adrian Bunk
2004-12-15 23:58 ` Alan Cox [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=1103155101.3585.26.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@stusta.de \
    --cc=g4klx@g4klx.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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).