netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: inaky@linux.intel.com
Cc: netdev@vger.kernel.org, wimax@linuxwimax.org, greg@kroah.com
Subject: Re: [PATCH 02/40] wimax: declarations for the in-kernel WiMAX API
Date: Fri, 05 Dec 2008 22:37:54 -0800 (PST)	[thread overview]
Message-ID: <20081205.223754.166106378.davem@davemloft.net> (raw)
In-Reply-To: <5fc227cf5709b01802959712ac23f519e65d4801.1228503077.git.inaky@linux.intel.com>

From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Date: Fri,  5 Dec 2008 10:54:55 -0800

> Declares the main data types and calls for the drivers to integrate
> into the WiMAX stack. Provides usage documentation.
> 
> Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>

This does:

+#include <linux/wimax.h>

which doesn't even exist yet.

I understand what you're trying to do, chop things up into manageable
pieces.  But this is taking it way too far.

It's totally impossible to review this patch on it's own, because none
of the necessary context exists at this point in the patch series.

I read this and wanted to know what enum wimax_st was, but that is
impossible to find because of this problem.

40 patches is, a lot, and I've now gone through this both in my inbox
and in my patch queue at patchwork.ozlabs.org 3 times.

You need to compact this a lot more if you want people to
review it without losing an entire day of their lives doing
so.

Thanks.

  reply	other threads:[~2008-12-06  6:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 18:54 [PATCH 00/40] merge request for WiMAX kernel stack and i2400m driver v3 Inaky Perez-Gonzalez
2008-12-05 18:54 ` [PATCH 01/40] wimax: documentation for the stack Inaky Perez-Gonzalez
2008-12-05 18:54 ` [PATCH 02/40] wimax: declarations for the in-kernel WiMAX API Inaky Perez-Gonzalez
2008-12-06  6:37   ` David Miller [this message]
2008-12-07  1:04     ` Inaky Perez-Gonzalez
2008-12-07  7:44       ` David Miller
2008-12-05 18:54 ` [PATCH 03/40] wimax: constants and definitions to interact with user space Inaky Perez-Gonzalez
2008-12-05 18:54 ` [PATCH 04/40] wimax: internal API for the kernel space WiMAX stack Inaky Perez-Gonzalez
2008-12-05 18:54 ` [PATCH 05/40] wimax: debug macros and debug settings for the " Inaky Perez-Gonzalez
2008-12-05 18:54 ` [PATCH 06/40] genetlink: export genl_unregister_mc_group() Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 07/40] debugfs: add helpers for exporting a size_t simple value Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 08/40] wimax: generic WiMAX device management (registration, deregistration, etc) Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 09/40] wimax: Mappping of generic netlink family IDs to net devices Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 10/40] wimax: Generic messaging interface between user space and driver/device Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 11/40] wimax: RF-kill framework integration Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 12/40] wimax: API call to reset a WiMAX device Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 13/40] wimax: debugfs controls Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 14/40] wimax: Makefile, Kconfig and docbook linkage for the stack Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 15/40] i2400m: documentation and instructions for usage Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 16/40] i2400m: host-to-device protocol definitions Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 17/40] i2400m: core driver definitions and API Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 18/40] i2400m: Generic probe/disconnect, reset and message passing Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 19/40] i2400m: linkage to the networking stack Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 20/40] i2400m: debugfs controls Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 21/40] i2400m: rfkill integration with the WiMAX stack Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 22/40] i2400m: firmware loading and bootrom initialization Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 23/40] i2400m: handling of the data/control reception path Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 24/40] i2400m: handling of the data/control transmission path Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 25/40] i2400m: various functions for device management Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 26/40] i2400m/USB: header for the USB bus driver Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 27/40] i2400m/USB: error density tracking Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 28/40] i2400m/USB: main probe/disconnect and backend routines Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 29/40] i2400m/USB: firmware upload backend Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 30/40] i2400m/USB: handling of notifications from the device Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 31/40] i2400m/USB: read transactions from the USB device Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 32/40] i2400m/USB: write transactions to " Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 33/40] i2400m/SDIO: header for the SDIO subdriver Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 34/40] i2400m/SDIO: main probe/disconnect and backend routines Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 35/40] i2400m/SDIO: firmware upload backend Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 36/40] i2400m/SDIO: read transactions from the SDIO device Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 37/40] i2400m/SDIO: write transactions to " Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 38/40] i2400m: Makefile and Kconfig Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 39/40] wimax: export linux/wimax.h and linux/wimax/i2400m.h with headers_install Inaky Perez-Gonzalez
2008-12-05 18:55 ` [PATCH 40/40] wimax/i2400m: add CREDITS and MAINTAINERS entries Inaky Perez-Gonzalez

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=20081205.223754.166106378.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=inaky@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wimax@linuxwimax.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;
as well as URLs for NNTP newsgroup(s).