public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <hermes@gibson.dropbear.id.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	jt@hpl.hp.com, Dan Williams <dcbw@redhat.com>,
	Pavel Roskin <proski@gnu.org>,
	Orinoco Development List <orinoco-devel@lists.sourceforge.net>
Subject: [0/15] orinoco merge preliminaries
Date: Wed, 28 Jul 2004 16:51:28 +1000	[thread overview]
Message-ID: <20040728065128.GC16908@zax> (raw)
In-Reply-To: <41068E4B.2040507@pobox.com>

On Tue, Jul 27, 2004 at 01:18:03PM -0400, Jeff Garzik wrote:
> >I've started to have a look at the patches.  Unfortunately, they're
> >still not really as logically separated as they should be.  Which I
> >guess means I wasn't sufficiently disciplined putting them into CVS in
> >the first place.
> >
> >I've started working on my own series of logical patches, starting
> >with, as you say the "content free" ones first.  Initial set with
> >series file at
> >       http://www.ozlabs.org/people/dgibson/orinoco-patches
> >
> >Nothing there so far that should cause any functional change.
> 
> 
> Feel free to start emailing them, so I can queue them up.
> 
> One email per patch, please.

Ok, patchbombing commences.

Following are 15 patches which make a start on merging the current CVS
orinoco driver into the mainline tree.  This batch of patches is only
preliminaries - patches which cause no behavioural change, but which
should be easy to review and which will reduce meaningless noise in
the later functional patches.

They all represent essentially trivial changes, and with the exception
of the rearrange patch (which is large because it moves big chunks of
code around) they should be obvious.  This batch of patches is
supposed to represent all the trivial, non-behaviour-changing
differences between orinoco CVS and mainline, though the merge is so
large, inevitably I will have missed a few.

Summary of the patches:
	1/15 orinoco-squash-backwards-compat:
		Removes old unnecessary backwards compatibility code
	2/15 orinoco-rearrange:
		Rearrange code so function order matches new versions
	3/15 orinoco-netdev-priv:
		Use netdev_priv() instead of direct dev->priv access
	4/15 orinoco-ALIGN:
		Use standard ALIGN macro instead of local versions
	5/15 orinoco-ARRAY-SIZE:
		Use ARRAY_SIZE macro instead of local version
	6/15 orinoco-spam-stoppers:
		Anti-spam obfuscate email addresses in source
	7/15 orinoco-comments-whitespace-spelling
		Whitespace/spelling/capitalisation updates
	8/15 orinoco-BUG-ON:
		Use BUG_ON() instead of explicit if () BUG() logic
	9/15 orinoco-add-statics:
		Make some functions static that always should have been
	10/15 orinoco-trivial-cleanup:
		Tiny changes than don't belong with anything else
	11/15 orinoco-driver-name-version:
		Reduce duplication of the driver names/version
	12/15 orinoco-uneeded-includes:
		Remove unnecessary #includes
	13/15 orinoco-no-struct-typedef:
		Don't use typedefs on simple structues
	14/15 orinoco-more-hw-data:
		Extra hw related #defines and structures
	15/15 orinoco-update-authorship:
		Update MAINTAINERS, copyright banners, etc.

-- 
David Gibson			| For every complex problem there is a
david AT gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

  reply	other threads:[~2004-07-28  7:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 19:33 [PATCH] Slowly update in-kernel orinoco drivers to upstream current CVS Francois Romieu
2004-07-14 18:37 ` Jeff Garzik
2004-07-15  1:01   ` David Gibson
2004-07-17 11:45     ` Francois Romieu
2004-07-27 17:18     ` Jeff Garzik
2004-07-28  6:51       ` David Gibson [this message]
2004-07-28  6:53         ` [1/15] orinoco merge preliminaries - squash backwards compatibility David Gibson
2004-07-28  6:53           ` [2/15] orinoco merge preliminaries - rearrange code David Gibson
2004-07-28  6:54             ` [3/15] orinoco merge preliminaries - use netdev_priv() David Gibson
2004-07-28  6:54               ` [4/15] orinoco merge preliminaries - use ALIGN() David Gibson
2004-07-28  6:55                 ` [5/15] orinoco merge preliminaries - use ARRAY_SIZE() David Gibson
2004-07-28  6:55                   ` [6/15] orinoco merge preliminaries - spam stoppers David Gibson
2004-07-28  6:56                     ` [7/15] orinoco merge preliminaries - comment/whitespace/spelling updates David Gibson
2004-07-28  6:57                       ` [8/15] orinoco merge preliminaries - use BUG_ON() David Gibson
2004-07-28  6:58                         ` [9/15] orinoco merge preliminaries - make things static David Gibson
2004-07-28  6:58                           ` [10/15] orinoco merge preliminaries - miscelaneous David Gibson
2004-07-28  6:59                             ` [11/15] orinoco merge preliminaries - use name/version macros David Gibson
2004-07-28  6:59                               ` [12/15] orinoco merge preliminaries - remove unneeded #includes David Gibson
2004-07-28  7:00                                 ` [13/15] orinoco merge preliminaries - don't typedef structs David Gibson
2004-07-28  7:00                                   ` [14/15] orinoco merge preliminaries - more HW data David Gibson
2004-07-28  7:01                                     ` [15/15] orinoco merge preliminaries - update authorship information David Gibson
2004-07-28 16:55                                       ` Jeff Garzik
2004-07-28 17:36                     ` [6/15] orinoco merge preliminaries - spam stoppers Matt Mackall
2004-07-28 22:50         ` [0/15] orinoco merge preliminaries Francois Romieu
2004-07-29  0:19           ` David Gibson
2004-07-29 23:19             ` Francois Romieu
2004-09-08 15:18               ` Dan Williams
2004-09-09  3:13                 ` Jeff Garzik
2004-09-09 19:51                   ` Francois Romieu
2004-07-14 20:15 ` [PATCH] Slowly update in-kernel orinoco drivers to upstream current CVS Pavel Roskin
2004-07-15  1:26   ` David Gibson

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=20040728065128.GC16908@zax \
    --to=hermes@gibson.dropbear.id.au \
    --cc=dcbw@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    --cc=proski@gnu.org \
    --cc=romieu@fr.zoreil.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