linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: linux-next: manual merge of the tip tree with the vfs tree
Date: Thu, 5 Jul 2012 15:00:12 +1000	[thread overview]
Message-ID: <20120705150012.63b7d7be0a0f549cfe650515@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next merge of the tip tree got a conflict in kernel/fork.c
between commit 7ab538da1f8a ("trim task_work: get rid of hlist") from the
vfs tree and commit 0ea86208345b ("sched, mm: Rework sched_{fork,exec}
node assignment") from the tip tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc kernel/fork.c
index bebabad,1a69745..0000000
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@@ -1414,8 -1415,7 +1415,7 @@@ static struct task_struct *copy_process
  	 * We dont wake it up yet.
  	 */
  	p->group_leader = p;
- 	INIT_LIST_HEAD(&p->thread_group);
 -	INIT_HLIST_HEAD(&p->task_works);
 +	p->task_works = NULL;
  
  	/* Now that the task is set up, run cgroup callbacks if
  	 * necessary. We need to run them before the task is visible

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

             reply	other threads:[~2012-07-05  5:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05  5:00 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-06  0:15 linux-next: manual merge of the tip tree with the vfs tree Stephen Rothwell
2020-10-01  6:34 Stephen Rothwell
2020-09-25  5:30 Stephen Rothwell
2020-07-27  5:35 Stephen Rothwell
2020-08-05  1:03 ` Stephen Rothwell
2018-11-26  4:39 Stephen Rothwell
2019-01-02  1:56 ` Stephen Rothwell
2018-06-22  1:53 Stephen Rothwell
2018-06-22  1:56 ` Stephen Rothwell
2018-06-22  6:13 ` Reinette Chatre
2018-06-22  6:56   ` Thomas Gleixner
2018-06-22 12:45 ` David Howells
2018-06-22 13:06   ` Al Viro
2018-06-22 13:39     ` Thomas Gleixner
2018-06-22 15:09       ` Reinette Chatre
2018-06-22 15:44         ` Thomas Gleixner
2016-09-29  2:57 Stephen Rothwell
2011-03-14  8:11 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=20120705150012.63b7d7be0a0f549cfe650515@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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).