mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ulrich Kunitz <kune@deine-taler.de>
To: Daniel Drake <dsd@gentoo.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	linville@tuxdriver.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/net/wireless/zd1211rw/: possible cleanups
Date: Mon, 17 Jul 2006 23:29:51 +0200	[thread overview]
Message-ID: <20060717212951.GC29824@p15091797.pureserver.info> (raw)
In-Reply-To: <44BA3C59.9030503@gentoo.org>

On 06-07-16 14:17 Daniel Drake wrote:

> Adrian Bunk wrote:
> >This patch contains the following possible cleanups:
> >- make needlessly global functions static
> >- #if 0 unused functions
> >
> >Please review which of these functions do make sense and which do 
> >conflict with pending patches.
> 
> Thanks Adrian. I have put this in my tree and made an additional change 
> along the same lines (your patched introduced an unused function warning 
> to the non-debug build). If Ulrich signifies acceptance, I will send 
> this on to John.
> 
> I have also sent in a patch to add a MAINTAINERS entry for zd1211rw, in 
> hope that this will help you send patches with myself and/or Ulrich CC'd 
> in future :)
> 
> Thanks.
> Daniel
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Adrian, I would like to see this patch split up into three at
least. 

Patch 1: Remove unused IO emulation functions
Patch 2: Remove other unused stuff, which could be split up
         further for each C file and header
Patch 3: Change DEBUG ifdefs to #if 0

The purpose of patch 3 is bogus, because the follow-up patch will
be called "removed useless #if 0 stuff". Keep in mind there is
some reason, why I have such code there. If they ifdefs are not
acceptable I will make this code dependent on a module parameter
and compile it into the production module. We have a lot of
different devices from different vendors out there and people
report "stuff isn't working" but almost nothing more.

The problem with patch 1 and 2 is, that almost all of the function
are completing the interface and some of them are even only static
inlines. They are there because they should be used, before
somebody reinvents the wheel or makes something completely stupid.
However if such reasoning is not acceptable I'm ready to
compromise.

-- 
Uli Kunitz

  reply	other threads:[~2006-07-17 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-15  0:35 Adrian Bunk
2006-07-16 13:17 ` Daniel Drake
2006-07-17 21:29   ` Ulrich Kunitz [this message]
2006-07-19 15:16     ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-07-09 17:53 Adrian Bunk

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=20060717212951.GC29824@p15091797.pureserver.info \
    --to=kune@deine-taler.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®