Re: [PATCH 3.10 00/11] 3.10.88-stable review

[Sudip Mukherjee]

On Sat, Sep 12, 2015 at 10:51:44AM -0700, Guenter Roeck wrote:
> On 09/12/2015 10:36 AM, Sudip Mukherjee wrote:
> >On Sat, Sep 12, 2015 at 07:22:39PM +0300, Max Filippov wrote:
> >>On Sat, Sep 12, 2015 at 6:55 PM, Greg Kroah-Hartman
> >><gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >>>On Sat, Sep 12, 2015 at 12:56:03PM +0530, Sudip Mukherjee wrote:
> >>>>On Fri, Sep 11, 2015 at 03:48:59PM -0700, Greg Kroah-Hartman wrote:
<snip>
> >>>>
> >>>>cross_compiled with allmodconfig:
> >>...
> >>>>xtensa - failed
> >>>
> >>>Are these all new failures?
> >>
> >>Build log says
> >>
> >>/home/travis/local/gcc-4.9.0-nolibc/xtensa-linux/bin/xtensa-linux-objcopy:
> >>Unable to change endianness of input file(s)
> >>make[2]: *** [arch/xtensa/boot/boot-elf/Image.o] Error 1
> >>
> >>which looks like misconfigured toolchain.
> >But the same script and same toolchain compiles properly for 4.1.7-rc1,
> >3.14.52-rc1 and also works for Linus tree (last tested yesterday
> >morning). I will see what has changed between 3.10 and 3.14 so that it
> >doesnot work for 3.10 but works for 3.14.
> >
> 
> The question here is if this is a new failure in 3.10, not if it has been
> fixed in a later kernel version.
> 
> For my part I used to report such persistent failures. However, I find it
> useless and even confusing to report "yep, still fails", unless there is
> a plan to fix it, so I don't do that anymore. Otherwise it is just a waste
> of test resources, and it makes it difficult to understand the test summary.
> 
> If I _do_ report such failures, I track down the cause and the fix, and ask
> the branch maintainer to apply the necessary patch(es).
I am trying to do the same with linux-next now. And as you suggested in
another reply just tried a clean build with 3.10.87 and that also failed.
I will find out the fix which caused it to build properly for 3.14 for
me.

regards
sudip
--
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/