From: "John W. Linville" <linville@tuxdriver.com>
To: Jonas Gorski <jogo@openwrt.org>
Cc: Fariya Fatima <fariya.f@redpinesignals.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3.14.0-rc5 v3 1/10] rsi: Adding RS9113 driver files
Date: Tue, 4 Mar 2014 15:13:13 -0500 [thread overview]
Message-ID: <20140304201313.GI7317@tuxdriver.com> (raw)
In-Reply-To: <CAOiHx==y9aSLA+Whr9A1xo7ikp7pDMtotc7=gPPZfPNLjap8rA@mail.gmail.com>
On Tue, Mar 04, 2014 at 09:08:26PM +0100, Jonas Gorski wrote:
> On Tue, Mar 4, 2014 at 7:38 PM, John W. Linville <linville@tuxdriver.com> wrote:
> > Does anyone have any last objections or criticisms to this patch series?
>
> > On Mon, Mar 03, 2014 at 01:25:38PM +0530, Fariya Fatima wrote:
> >> Kconfig | 1
> >> Makefile | 1
>
> A minor critique would be that these Kconfig/Makefile changes should
> be added in the last patch, else any in-between will result in a state
> where the driver is selectable, but fails to build because of missing
> source files.
FWIW, I tend to collapse a series like this (i.e. one that adds a new
driver using a series of small, non-buildable patches) into a single
patch when merging.
> Also the subject suggests the patch set was based on linus' tree, not
> wireless-next (or whatever the correct tree is), but this does not
> necessarily mean it does not apply; I did not test this.
This is usually not a (big) merge problem for a new driver.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-03-04 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 7:55 [PATCH 3.14.0-rc5 v3 1/10] rsi: Adding RS9113 driver files Fariya Fatima
2014-03-04 18:38 ` John W. Linville
2014-03-04 20:08 ` Jonas Gorski
2014-03-04 20:13 ` John W. Linville [this message]
2014-03-05 10:49 ` Johannes Berg
[not found] <-1822401706-40502@mail.redpinesignals.com>
2014-03-05 18:08 ` Johannes Berg
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=20140304201313.GI7317@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=fariya.f@redpinesignals.com \
--cc=jogo@openwrt.org \
--cc=linux-wireless@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.