Hey guys ,
I checking Sachin Karmat's tests and fixing compile issues with
patches if need be. In my next email I am going to give a up to date
log of still failing builds for arm.
Cheers Nick
On Sat, Jul 5, 2014 at 10:57 AM, Sachin Kamat <spk.linux@xxxxxxxxx> wrote:
> On Sat, Jul 5, 2014 at 6:18 AM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
>> On Sat, Jul 05, 2014 at 01:10:58AM +1000, Stephen Rothwell wrote:
>>> Hi Sachin,
>>>
>>> On Fri, 4 Jul 2014 14:12:11 +0530 Sachin Kamat <spk.linux@xxxxxxxxx> wrote:
>>> >
>>> > Was bisecting a kernel crash on Arndale octa board (Exynos5420). It
>>> > points to a merge
>>> > commit:
>>> > 40556a4c485d12d324f1ea196cc30f590e564237 is the first bad commit
>>> > ("Merge remote-tracking branch 'nfsd/nfsd-next'").
>>> >
>>> > How do I proceed with this?
>>>
>>> I guess we get the owner of the tree (possibly) in question involved
>>> (cc'd).
>>
>> Looking at the total diffstat for that branch, it's almost all contained
>> in fs/nfsd with a little in include/linux/sunrpc/ and net/sunrpc. So
>> it's extremely unlikely that it would be causing a problem unless you're
>> actually testing nfsd.
>
> I found it surprising too as I do not use nfsd. I will try out the things
> suggested by Stephen and update.
>
> --
> Regards,
> Sachin.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
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
