public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: jgarzik@mandrakesoft.com, orinoco-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: Cosmetic updates for orinoco driver
Date: Thu, 4 Nov 2004 13:12:28 +1100	[thread overview]
Message-ID: <20041104021228.GA3949@zax> (raw)
In-Reply-To: <20041103154407.4d9833ca.akpm@osdl.org>

On Wed, Nov 03, 2004 at 03:44:07PM -0800, Andrew Morton wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > This patch reformats printk()s and some other cosmetic strings in the
> > orinoco driver.  Also moves, removes, and adds ratelimiting in some
> > places.  Behavioural changes are trivial/cosmetic only.  This reduces
> > the cosmetic/trivial differences between the current kernel version,
> > and the CVS version of the driver; one small step towards full merge.
> 
> This produces a ghastly reject storm against Jeff's bk-netdev tree.
> 
> I dunno how Jeff wants to handle that.  I stuck a copy of his current patch
> (against 2.6.10-rc1) at
> http://www.zip.com.au/~akpm/linux/patches/stuff/bk-netdev.patch and shall
> now run away.

Ah, looks like Al Viro did the ioread/iowrite conversion while I
wasn't looking.  Ok, with that netdev patch I should be able to fix
things up (and merge the iowrite conversion back into CVS).

-- 
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-11-04  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03  2:24 Cosmetic updates for orinoco driver David Gibson
2004-11-03 23:44 ` Andrew Morton
2004-11-04  2:12   ` David Gibson [this message]
2004-11-05  2:46     ` Jeff Garzik
2004-11-05  4:38       ` 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=20041104021228.GA3949@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=akpm@osdl.org \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    /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