All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] remove code for WIRELESS_EXT < 18
Date: Sun, 4 Dec 2005 20:52:07 +0100	[thread overview]
Message-ID: <20051204195207.GA9973@stusta.de> (raw)
In-Reply-To: <4393447E.3020003@pobox.com>

On Sun, Dec 04, 2005 at 02:33:18PM -0500, Jeff Garzik wrote:
> Adrian Bunk wrote:
> >WIRELESS_EXT < 18 will never be true in the kernel.
> >
> >
> >Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> >---
> >
> > drivers/net/wireless/ipw2100.c           |  434 ----------------------
> > drivers/net/wireless/tiacx/acx_struct.h  |    5 
> > drivers/net/wireless/tiacx/common.c      |    4 
> > drivers/net/wireless/tiacx/conv.c        |    2 
> > drivers/net/wireless/tiacx/ioctl.c       |  441 -----------------------
> > drivers/net/wireless/tiacx/pci.c         |    8 
> > drivers/net/wireless/tiacx/usb.c         |    6 
> > drivers/net/wireless/tiacx/wlan.c        |    2 
> > drivers/net/wireless/tiacx/wlan_compat.h |    9 
> > 9 files changed, 1 insertion(+), 910 deletions(-)
> 
> NAK, patches non-existent files.
> 
> [jgarzik@pretzel linux-2.6]$ ls drivers/net/wireless/tiacx
> ls: drivers/net/wireless/tiacx: No such file or directory

As the subject says, it's against -mm.

How should I resend it?
One patch against ipw2100.c and one patch for the tiacx stuff?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2005-12-04 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 12:27 [-mm patch] remove code for WIRELESS_EXT < 18 Adrian Bunk
2005-12-04 19:33 ` Jeff Garzik
2005-12-04 19:52   ` Adrian Bunk [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=20051204195207.GA9973@stusta.de \
    --to=bunk@stusta.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.