From: Sedat Dilek <sedat.dilek@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: mmotm 2013-01-11-15-47 uploaded (x86 asm-offsets broken)
Date: Sat, 12 Jan 2013 12:12:15 +0100 [thread overview]
Message-ID: <CA+icZUXVJPrV7-hPa3GNtabijXvktY6tHqKMJ3u5vm-fQV4+fg@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUVMY76bRFgUumZy0G-FFM=80iwfSFSopHMwHRYfgKjLjA@mail.gmail.com>
On Sat, Jan 12, 2013 at 11:13 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Sat, Jan 12, 2013 at 3:29 AM, Joe Perches <joe@perches.com> wrote:
>> On Sat, 2013-01-12 at 13:17 +1100, Stephen Rothwell wrote:
>>> On Fri, 11 Jan 2013 17:43:06 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>>> >
>>> > b0rked.
>>> >
>>> > Some (randconfig?) causes this set of errors:
>>
>> I guess that's when CONFIG_HZ is not an even divisor of 1000.
>> I suppose this needs to be worked on a bit more.
>>
>>
>
> I remember this patch from Joe come up with a pending patch in
> net-next.git#master [1] (I mention this as I have not seen hit it in
> latest Linux-Next whereas this latest mmotm includes it [2]).
>
> $ grep "config HZ_" kernel/Kconfig.hz
> config HZ_100
> config HZ_250
> config HZ_300
> config HZ_1000
>
> As I see Randy has in his kernel-config:
>
> # CONFIG_HZ_100 is not set
> # CONFIG_HZ_250 is not set
> CONFIG_HZ_300=y
> # CONFIG_HZ_1000 is not set
> CONFIG_HZ=300
>
> So there is a problem for the value "300" (only)?
>
> Regards,
> - Sedat -
>
>
> [1] http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=c10d73671ad30f54692f7f69f0e09e75d3a8926a
> [2] http://git.cmpxchg.org/?p=linux-mmotm.git&a=search&h=HEAD&st=commit&s=softirq
>
That is the patch by Joe in question: "jiffies conversions: Use
compile time constants when possible" (see also [1]).
- Sedat -
[1] http://git.cmpxchg.org/?p=linux-mmotm.git;a=commitdiff;h=049aaaabf2476318f9a2708e3cbd2b2c937faeb0
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-next" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-12 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 23:48 mmotm 2013-01-11-15-47 uploaded akpm
2013-01-12 1:43 ` mmotm 2013-01-11-15-47 uploaded (x86 asm-offsets broken) Randy Dunlap
2013-01-12 2:17 ` Stephen Rothwell
2013-01-12 2:29 ` Joe Perches
2013-01-12 10:13 ` Sedat Dilek
2013-01-12 11:12 ` Sedat Dilek [this message]
2013-01-12 16:52 ` Joe Perches
2013-01-14 4:03 ` Stephen Rothwell
2013-01-12 15:47 ` mmotm 2013-01-11-15-47 (trouble starting kvm) Zlatko Calusic
2013-01-15 18:46 ` Jiri Kosina
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=CA+icZUXVJPrV7-hPa3GNtabijXvktY6tHqKMJ3u5vm-fQV4+fg@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).