Re: linux-next broken by "ARM: S3C2440: move mach-s3c2440/* into mach-s3c24xx/"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12-03-08 02:12 PM, Mark Brown wrote:
> On Thu, Mar 08, 2012 at 11:23:26AM -0500, Paul Gortmaker wrote:
>> Something bad happened in this commit (dd6f01b5cc).  It looks like
>> the moved file is truncated, causing this failure:
> 
>> http://kisskb.ellerman.id.au/kisskb/buildresult/5818815/
> 
>> I believe it came in via the fix/asoc tree.
> 
> Hrm?  What is "it" in this context, and what was your analysis here?
> Nothing in the page you're linking to above suggests something audio
> related...

The "it" was the commit in the subject, and the ID in the above text.
That was the last commit to have touched this file (via moving it).

What I took as a relation to fix/asoc was shown in the text you've
gone and deleted here in the follow up.

In any case, it does appear the file was broken before it was moved.
The offending commit is actually c1ba544f81544ed9613ad5d058968533dbcef4b2

	"ARM: S3C24XX: Fix restart on S3C2442"

It appears that a closing brace was dropped when it was integrated.

Paul.


--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux