linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Kelly <ckelly@ozmodevices.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (staging tree related)
Date: Wed, 29 Feb 2012 18:52:27 +1100	[thread overview]
Message-ID: <20120229185227.7f14b1863c7a5d16220bac3f@canb.auug.org.au> (raw)
In-Reply-To: <57C28D85C66F5C49B9E212CBFAFDAC1F23010F80@CH1PRD0802MB120.namprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

Hi Chris,

On Wed, 29 Feb 2012 07:35:35 +0000 Chris Kelly <ckelly@ozmodevices.com> wrote:
>
> Hi Greg,
> 
> I believe I understand the cause of the problem and would like to submit
> a patch to fix it. However, I am unclear on what the starting point is given
> that the final patch was reverted from linux-next. Do I assume that patch
> will be reapplied before the applying the new patch or should I provide
> another patch to reapply the reverted patch? Is it acceptable to submit
> patches generated against the head of linux-next?

Your patches are all still in Greg's tree which I merge into linux-next
every day.  I have then been reverting that last patch each day.  Your
patch should be against Greg's tree (or your last patch) and then when
the fix is in Greg's tree, I will get it in linux-next and stop reverting
the other patch.

> Before submitting the patch, I would like to test that the patch really
> does fix the issue found by Stephen. Since it doesn't occur when building
> for x32 or x64 then I need to setup a PowerPC cross-compile tool chain. Do
> you have any suggestions as to where I can pull a prebuilt tool chain or
> do I need to build directly from the GNU sources.

http://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_powerpc64-linux.tar.xz

That is am x86_64 hosted powerpc64 compiler suitable for building the
kernel.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-29  7:52 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  7:13 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2012-02-27 21:16 ` Greg KH
2012-02-29  7:35   ` Chris Kelly
2012-02-29  7:52     ` Stephen Rothwell [this message]
2012-02-29 17:08       ` Chris Kelly
  -- strict thread matches above, loose matches on Subject: below --
2014-02-10  4:54 Stephen Rothwell
2014-02-10  5:04 ` Greg KH
2013-06-19  8:10 Stephen Rothwell
2013-06-19  9:26 ` Peng Tao
2013-06-19 14:37   ` Greg KH
2013-06-20 10:52     ` Peng Tao
2013-06-24 22:40   ` Greg KH
2013-06-24 23:40     ` Stephen Rothwell
2013-06-24 23:50       ` Greg KH
2013-06-25  0:22         ` Peng Tao
2013-06-25  2:13           ` Greg KH
2013-04-24  7:56 linux-next: build failure after merge of the final tree (staging tree related)) Stephen Rothwell
2013-04-24 17:53 ` H Hartley Sweeten
2013-04-24 18:33 ` H Hartley Sweeten
2013-03-13  5:39 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2013-03-14 20:23 ` Paul Zimmerman
2013-03-14 20:33   ` Greg KH
2013-03-06  0:35 Stephen Rothwell
2013-03-06  0:43 ` Greg KH
2013-03-06 13:56   ` Konrad Rzeszutek Wilk
2013-03-06 20:04     ` Konrad Rzeszutek Wilk
2013-03-06 20:46       ` Stephen Rothwell
2013-03-06 20:50       ` Stephen Rothwell
2013-03-06 22:23         ` Konrad Rzeszutek Wilk
2013-03-06 22:11       ` Greg KH
2013-03-06 22:21         ` Konrad Rzeszutek Wilk
2012-11-13  5:51 Stephen Rothwell
2012-11-13  9:24 ` Jonathan Cameron
2012-11-13 18:48 ` Greg KH
2012-09-24 14:29 Stephen Rothwell
2012-09-10  7:04 Stephen Rothwell
2012-09-10 17:31 ` Greg KH
2012-09-05  5:48 Stephen Rothwell
2012-09-06 18:06 ` Geert Uytterhoeven
2012-05-16 10:06 Stephen Rothwell
2012-05-16 12:49 ` Greg KH
2012-05-16 14:17   ` Dan Magenheimer
2012-05-16 15:10     ` Greg KH
2012-02-13  6:19 Stephen Rothwell
2012-02-13  6:45 ` Greg KH
2012-02-13 14:13   ` Seth Jennings
2012-02-13 14:48   ` Seth Jennings
2012-02-13 15:03     ` Greg KH
2011-10-04  8:05 Stephen Rothwell
2011-10-04  8:49 ` Jonathan Cameron
2011-08-25  6:17 Stephen Rothwell
2011-08-24  5:47 Stephen Rothwell
2011-08-24 21:16 ` Greg KH
2011-08-24 22:54   ` Stephen Rothwell
2011-08-24 22:57     ` Greg KH
2011-08-24 23:28       ` Stephen Rothwell
2011-07-18  9:36 Stephen Rothwell
2011-07-19  1:01 ` Greg KH
2011-07-28  3:35   ` Stephen Rothwell
2011-08-02 23:17     ` Greg KH
2011-07-07  6:25 Stephen Rothwell
2011-07-07 13:44 ` Greg KH

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=20120229185227.7f14b1863c7a5d16220bac3f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ckelly@ozmodevices.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).