From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-next@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: linux-next: manual merge of the vfs tree
Date: Wed, 25 Jun 2008 15:47:32 +1000 [thread overview]
Message-ID: <20080625154732.23abbb9d.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Hi Al,
Today's linux-next merge of the vfs tree got a trivial contextual
conflict in kernel/sysctl.c between commit
31a72bce0bd6f3e0114009288bccbc96376eeeca ("rcu: make rcutorture more
vicious: reinstate boot-time testing") from the sched tree and commit
5f12804f188a8f2fe6d7fdb5c1b9a4340cfa0458 ("[PATCH] avoid multiplication
overflows and signedness issues for max_fds") from the vfs tree (which is
also in Linus' tree).
I just fixed it up and will carry the fixup.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-06-25 5:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 5:47 Stephen Rothwell [this message]
2008-07-18 5:27 linux-next: manual merge of the vfs tree Stephen Rothwell
2008-07-18 9:44 ` Stephen Rothwell
2008-07-18 5:33 Stephen Rothwell
2008-07-18 5:36 Stephen Rothwell
2008-07-18 8:33 ` Ralf Baechle
2008-07-18 9:06 ` Stephen Rothwell
2008-07-18 12:51 ` Al Viro
2008-07-25 4:30 Stephen Rothwell
2008-08-12 5:01 Stephen Rothwell
2008-08-12 5:14 Stephen Rothwell
2008-08-12 5:20 Stephen Rothwell
2008-08-12 19:27 ` J. Bruce Fields
2008-08-19 5:23 Stephen Rothwell
2008-08-19 5:25 Stephen Rothwell
2008-10-15 6:50 Stephen Rothwell
2013-09-30 11:26 linux-next: manual merge of the bcon tree Thierry Reding
2013-09-30 11:26 ` linux-next: manual merge of the vfs tree Thierry Reding
2013-10-01 11:03 linux-next: Tree for Oct 1 Thierry Reding
2013-10-01 11:07 ` linux-next: manual merge of the vfs tree Thierry Reding
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=20080625154732.23abbb9d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--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).