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
Subject: Re: linux-next: sysctl tree build failure
Date: Thu, 12 Nov 2009 01:11:34 -0800 [thread overview]
Message-ID: <m1fx8kp0op.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20091112191451.d21250f2.sfr@canb.auug.org.au> (Stephen Rothwell's message of "Thu\, 12 Nov 2009 19\:14\:51 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Eric,
>
> On Thu, 12 Nov 2009 00:08:59 -0800 ebiederm@xmission.com (Eric W. Biederman) wrote:
>>
>> Thank you, and my apologies. I thought I had tried it with every
>> applicable compile option but apparently not.
>>
>> Ugh. It looks like I have a small refcount leak in that case as
>> well. Blind I was.
>>
>> Thank you very I will have this fixed shortly.
>
> Thanks.
Any clue how all_noconfig happened to have CONFIG_SYSCTL_SYSCALL set?
Eric
next prev parent reply other threads:[~2009-11-12 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 7:48 linux-next: sysctl tree build failure Stephen Rothwell
2009-11-12 8:08 ` Eric W. Biederman
2009-11-12 8:14 ` Stephen Rothwell
2009-11-12 9:11 ` Eric W. Biederman [this message]
2009-11-12 10:47 ` Stephen Rothwell
2009-11-12 12:10 ` 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=m1fx8kp0op.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--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