From: Oleg Nesterov <oleg@redhat.com>
To: David Miller <davem@davemloft.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
matt.fleming@intel.com, tj@kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (sparc, ptrace trees related)
Date: Fri, 14 Oct 2011 21:09:50 +0200 [thread overview]
Message-ID: <20111014190950.GA10791@redhat.com> (raw)
In-Reply-To: <20111014.035459.2238341687770152474.davem@davemloft.net>
On 10/14, David Miller wrote:
>
> Now you guys are creating conflicts against those fixed up patches in
> another non-sparc tree, and adding new kinds of build failures as
> well.
>
> This doesn't work.
Sorry David and Stephen.
Stephen, could you please temporary remove ptrace from linux-next?
I'll send you another email once I fix the conflicts, can't do this
right now.
Oleg.
next prev parent reply other threads:[~2011-10-14 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 7:07 linux-next: build failure after merge of the final tree (sparc, ptrace trees related) Stephen Rothwell
2011-10-14 7:54 ` David Miller
2011-10-14 9:27 ` Matt Fleming
2011-10-14 11:38 ` Stephen Rothwell
2011-10-14 19:09 ` Oleg Nesterov [this message]
2011-10-24 9:36 ` 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=20111014190950.GA10791@redhat.com \
--to=oleg@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=tj@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).