linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Ken Chen <kenchen@google.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v42] proc: add /proc/*/stack (was Re: linux-next: proc tree build failure)
Date: Mon, 10 Nov 2008 09:49:00 +0100	[thread overview]
Message-ID: <20081110084900.GF22392@elte.hu> (raw)
In-Reply-To: <20081110084229.GA8690@x200.localdomain>


* Alexey Dobriyan <adobriyan@gmail.com> wrote:

> > Alexey, would you like to carry them for v2.6.29? They are in a 
> > separate tree here, the pull coordinates are below.
> > 
> > Please preserve the sha1's (do not rebase/cherry-pick, etc.) so 
> > that i can carry it too without causing confusion.
> 
> Sorry, I can't.

hm, git pull did not work?

> It's two commits, PROC_BLOCK_SIZE moving chunk is now unneeded, 
> because seqfiles are in use, grabbing tasklist_lock for protection 
> from task dissapearing is unneeded -- proc_single_show() pins 
> task_struct, entry is added only to tgid table.

hm, but these are small differences that do not impact bisectability, 
you could have done it ontop of what we have, instead of a rebase? Oh 
well.

> So, here is final version:

thanks!

I've rebased tip/core/stacktrace and zapped the history of the old 
commits from that branch. Would have been really nice to preserve the 
sha1 space and not force a rebase, like Linus is requesting it so 
frequently.

Had you done a git pull from me i could have carried this feature too 
without creating conflicts, instead of it disappearing in your tree 
for months and being hidden up until v2.6.29. This whole 'distributed 
development' stuff that's all the rage ;-)

i also regenerated tip-core, so it should now be conflict-free in 
Stephen's tree too. (Stephen, please holler if you still get 
conflicts)

	Ingo

      reply	other threads:[~2008-11-10  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081110162941.e9e9ef3a.sfr@canb.auug.org.au>
     [not found] ` <20081110055311.GA3138@x200.localdomain>
     [not found]   ` <20081110073623.GA475@elte.hu>
2008-11-10  8:42     ` [PATCH v42] proc: add /proc/*/stack (was Re: linux-next: proc tree build failure) Alexey Dobriyan
2008-11-10  8:49       ` Ingo Molnar [this message]

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=20081110084900.GF22392@elte.hu \
    --to=mingo@elte.hu \
    --cc=adobriyan@gmail.com \
    --cc=kenchen@google.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).