From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Octavian Purdila <opurdila@ixiacom.com>,
Cosmin Ratiu <cratiu@ixiacom.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: manual merge of the sysctl tree with the net tree
Date: Tue, 17 Nov 2009 01:17:47 -0800 [thread overview]
Message-ID: <m17htph5ms.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20091117190401.94f6b5cb.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Tue\, 17 Nov 2009 19\:04\:01 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Eric,
>
> Today's linux-next merge of the sysctl tree got a conflict in
> net/ipv6/addrconf.c between commit
> f7734fdf61ec6bb848e0bafc1fb8bad2c124bb50 ("make TLLAO option for NA
> packets configurable") from the net tree and commit
> f8572d8f2a2ba75408b97dc24ef47c83671795d7 ("sysctl net: Remove unused
> binary sysctl code") from the sysctl tree.
>
> I fixed it up (see below) including removing the new ctl_name (thanks for
> the heads up, Eric). I can carry this fixup as necessary.
Would it be of any value for me to send David a change killing ctl_name
for the new entry? That is equivalent to .ctl_name = CTL_UNNUMBERED and
would make this a trivial conflict.
Fundamentally the conflict detection will always kick in here because
as I am modifying previous and succeeding entries in the table so the
context will always be different.
I'm still getting a hang of running a public git tree.
Eric
> diff --cc net/ipv6/addrconf.c
> index 522bdc7,f918399..0000000
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@@ -4388,15 -4285,7 +4320,14 @@@ static struct addrconf_sysctl_tabl
> .proc_handler = proc_dointvec,
> },
> {
> - .ctl_name = CTL_UNNUMBERED,
> + .procname = "force_tllao",
> + .data = &ipv6_devconf.force_tllao,
> + .maxlen = sizeof(int),
> + .mode = 0644,
> + .proc_handler = proc_dointvec
> + },
> + {
> - .ctl_name = 0, /* sentinel */
> + /* sentinel */
> }
> },
> };
next prev parent reply other threads:[~2009-11-17 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 8:04 linux-next: manual merge of the sysctl tree with the net tree Stephen Rothwell
2009-11-17 9:17 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-30 5:44 Stephen Rothwell
2009-11-30 5:51 ` Américo Wang
2009-11-30 6:39 ` Eric W. Biederman
2009-11-30 9:26 ` Américo Wang
2009-11-30 6:41 ` Stephen Rothwell
2009-11-30 9:21 ` Américo Wang
2009-12-01 14:13 ` Vlad Yasevich
2009-12-04 8:36 Stephen Rothwell
2009-12-04 8:36 ` Stephen Rothwell
2009-12-04 8:50 ` Eric W. Biederman
2009-12-04 8:50 ` Eric W. Biederman
2009-12-04 8:43 Stephen Rothwell
2009-12-04 8:43 ` Stephen Rothwell
2009-12-04 12:16 ` William Allen Simpson
2009-12-04 12:21 ` Stephen Rothwell
2009-12-04 21:42 ` Eric W. Biederman
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=m17htph5ms.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=cratiu@ixiacom.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.