linux-kernel - Re: [PATCH 1/5] drivers: net: usb: rtl8150: moving constant and structure definitions out of rtl8150.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1305202158520.3400@fry.nucleusys.com>
Date:	Mon, 20 May 2013 22:08:32 +0300 (EEST)
From:	Petko Manolov <petkan@...leusys.com>
To:	Ben Hutchings <bhutchings@...arflare.com>
cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] drivers: net: usb: rtl8150: moving constant and
 structure definitions out of rtl8150.c

On Mon, 20 May 2013, Ben Hutchings wrote:

> Now how is this driver going to compile, when rtl8150.h is only added by
> the next patch?!

I got carried away by the desire to make each patch smaller and to the 
point.  Sacrificing build-ability of the tree, however, does not justify 
it.  My bad.

> You need to squash these first 2 together, so that the driver can be
> compiled after each step.

Will do once David merge 'net' into 'net-next'.


		Petko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/