From: ebiederm@xmission.com (Eric W. Biederman)
To: Ingo Molnar <mingo@elte.hu>
Cc: Joe Perches <joe@perches.com>,
Am??rico Wang <xiyou.wangcong@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sysctl.c: Change a .proc_handler = proc_dointvec to &proc_dointvec,
Date: Sun, 15 Nov 2009 06:14:45 -0800 [thread overview]
Message-ID: <m1bpj3lvsa.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20091115135705.GA9329@elte.hu> (Ingo Molnar's message of "Sun\, 15 Nov 2009 14\:57\:05 +0100")
Ingo Molnar <mingo@elte.hu> writes:
> The preferred flow is for you to just work against Linus's latest tree -
> and everyone will deal with the (mostly trivial) conflicts when they
> happen. Linus prefers to resolve conflicts himself when he pulls,
> because people mixing their trees (such as you basing on net-next for
> example) leads to various dependency problems.
Sounds right.
I'm still getting up the courage to conflict. I was wondering if I
could cherry pick a patch or two to avoid those.
Right now in the net tree there is one new sysctl and one bug fix to a
sysctl strategy routine I intend to delete.
The core or my changes are in. This is just purging dead code.
It looks like those two changes may actually be single patches so I
could cherry pick them and in theory have no conflicts.
At the very least I'm going to wait for one more build of net-next with
everything but my network stack changes before I add those.
So far the conflicts are pretty minimal so I guess it doesn't matter
much.
Eric
next prev parent reply other threads:[~2009-11-15 14:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 1:52 [PATCH] sysctl.c: Change a .proc_handler = proc_dointvec to &proc_dointvec, Joe Perches
2009-11-15 6:59 ` Américo Wang
2009-11-15 8:11 ` Ingo Molnar
2009-11-15 8:28 ` Joe Perches
2009-11-15 8:39 ` Ingo Molnar
2009-11-15 10:04 ` Eric W. Biederman
2009-11-15 10:33 ` Ingo Molnar
2009-11-15 12:29 ` Eric W. Biederman
2009-11-15 13:57 ` Ingo Molnar
2009-11-15 14:14 ` Eric W. Biederman [this message]
2009-11-15 17:31 ` Joe Perches
2009-11-15 18:20 ` Julia Lawall
2009-11-15 19:23 ` Joe Perches
2009-11-15 20:40 ` Julia Lawall
2009-11-15 20:53 ` Arnd Bergmann
2009-11-15 22:54 ` Julia Lawall
2009-11-15 21:13 ` Joe Perches
2009-11-15 21:34 ` Julia Lawall
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=m1bpj3lvsa.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=xiyou.wangcong@gmail.com \
/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