Linux wireless drivers development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>,
	bzolnier@gmail.com,
	Bernhard Schiffner <bernhard@schiffner-limbach.de>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFT 0/6] rtl8187se: Initial introduction of driver
Date: Tue, 10 Nov 2009 10:25:03 +0100	[thread overview]
Message-ID: <1257845103.26914.5.camel@violet> (raw)
In-Reply-To: <4af8a56a.fCJY51VFS93aEZ0t%Larry.Finger@lwfinger.net>

Hi Larry,

> Patches to introduce a driver for the RTL8187SE PCI-based device.
> 
> Note: This driver is only compile-tested and will require more work
> for it to be useful. I'm posting now to let others know what I have done.
> 
> I have applied for an account at kernel.org. If my request is approved, I
> plan to establish an rtl8187se git tree.
> 
> Patch 1/6: Create file rtl8187se.h
> Patch 2/6: Create file rtl8187se_dev.c
> Patch 3/6: Create file rtl8187se_rtl8225.c
> Patch 4/6: Create file rtl8187se_rtl8225.h
> Patch 5/6: Modify file rtl818x.h
> Patch 6/6: Modify Kconfig and Makefile for rtl8187se

so personally I don't think the split in a per file commit is helpful at
all. It adds no real value to the tree. For review and working around
the size limit of vger.kernel.org it is fine, but for the final merge I
prefer that all files are added in one commit.

Regards

Marcel



  reply	other threads:[~2009-11-10  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 23:27 [RFT 0/6] rtl8187se: Initial introduction of driver Larry Finger
2009-11-10  9:25 ` Marcel Holtmann [this message]
2009-11-10 13:34   ` John W. Linville
2009-11-10 15:39     ` Larry Finger

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=1257845103.26914.5.camel@violet \
    --to=marcel@holtmann.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bernhard@schiffner-limbach.de \
    --cc=bzolnier@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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