All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: sudipm.mukherjee@gmail.com
Cc: sfr@canb.auug.org.au, starvik@axis.com, jespern@axis.com,
	netdev@vger.kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com,
	jhs@mojatatu.com
Subject: Re: linux-next: Tree for Oct 6
Date: Wed, 7 Oct 2015 15:31:51 +0200	[thread overview]
Message-ID: <201510071331.t97DVpgB031864@ignucius.se.axis.com> (raw)
In-Reply-To: <20151007071046.GA21158@sudip-pc> (message from Sudip Mukherjee on Wed, 7 Oct 2015 09:10:46 +0200)

> From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> Date: Wed, 7 Oct 2015 09:10:46 +0200

> On Tue, Oct 06, 2015 at 04:46:53PM +0200, Hans-Peter Nilsson wrote:
> > Thanks for the heads-up, but any chance of a bug report as per
> > the instructions in the message?  It'll only speed up matters.
> I can try, but since I am using 4.6.3 version I doubt if I will get the
> required response (Happened with another arch).

Ow, way old.

> And this is the latest
> cris cross-compiler available in
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/

I have nothing to do with that.

> BTW, I did a bisect and if I revert 47bbbb30b433 ("sch_dsmark: improve memory locality")
> it again builds without any error.

Sorry, that's not really useful to me, neither are build logs.
What I need to proceed with fixing is preprocessed code and the
compiler options used, just as the bug-reporting instructions
say.  Now that I hear that you get the ICE with a really old gcc
version, I'm not inclined to look further, sorry.  Except, when
you mention the version I vaguely remember; it reminds me of a
bug fixed a long time ago.  Maybe it was PR53120?  Sorry, I
don't remember anything else useful.  Still, thanks; it'll
shorten the response time if other people tell me the same
thing.

brgds, H-P


  reply	other threads:[~2015-10-07 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  7:25 linux-next: Tree for Oct 6 Stephen Rothwell
2015-10-06 11:20 ` [PATCH] pwm: bcm7038: fix build failure Sudip Mukherjee
2015-10-06 11:20   ` Sudip Mukherjee
2015-10-06 12:33 ` linux-next: Tree for Oct 6 Sudip Mukherjee
2015-10-06 13:24   ` David Miller
2015-10-06 14:46   ` Hans-Peter Nilsson
2015-10-07  7:10     ` Sudip Mukherjee
2015-10-07 13:31       ` Hans-Peter Nilsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-06 12:38 Mark Brown
2023-10-06  4:38 Stephen Rothwell
2022-10-06  7:38 Stephen Rothwell
2021-10-06  7:56 Stephen Rothwell
2020-10-06 12:12 Stephen Rothwell
2016-10-06  3:23 Stephen Rothwell
2011-10-06  6:28 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201510071331.t97DVpgB031864@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=davem@davemloft.net \
    --cc=jespern@axis.com \
    --cc=jhs@mojatatu.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=starvik@axis.com \
    --cc=sudipm.mukherjee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.