From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Fri, 16 Oct 2015 14:31:10 -0700
Subject: I have a large patch in the 2000 lines. What to do?
In-Reply-To: <CAENf94LAfnJaDDUv9k8By-yTC4kSyw-2iHb+QMDfkdGz3qwAWw@mail.gmail.com>
References: <56180B3F.9040208@gmail.com>
	<AD20A93C-563F-49A1-905C-397299ABB584@gmail.com>
	<20151009192048.GA16217@kroah.com> <561863B9.4010000@gmail.com>
	<20151010141446.GB6080@kroah.com>
	<CAENf94LAfnJaDDUv9k8By-yTC4kSyw-2iHb+QMDfkdGz3qwAWw@mail.gmail.com>
Message-ID: <20151016213110.GA23593@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org



On Fri, Oct 16, 2015 at 06:14:01PM -0300, Julio Faracco wrote:
> 
> What is the recommendation when I change a structure in a include file
> and this change causes a lots of new changes, for example?

You do the change in a way that does not cause build failures and spread
the patches out over all subsystems to fix things up.

Do you have a specific example you were thinking of so that I can show
how it can be done in this way?

thanks,

greg k-h