public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte•hu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
	linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
	netfilter-devel@vger•kernel.org, apw@shadowen•org,
	Franck Bui-Huu <fbuihuu@gmail•com>,
	Andrew Morton <akpm@linux-foundation•org>
Subject: Re: [PATCH] linux-next: Tree for May 21 - build failure with netfilter on __nf_ct_helper_find()
Date: Thu, 22 May 2008 10:15:46 +0200	[thread overview]
Message-ID: <20080522081546.GB7222@elte.hu> (raw)
In-Reply-To: <20080522101148.fbabee96.sfr@canb.auug.org.au>


* Stephen Rothwell <sfr@canb•auug.org.au> wrote:

> Actually this is caused by the splitting out of the rcu stuff from 
> list.h that is in linux-next, sorry.

this bug has been fixed in the -tip tree 9 days ago:

|  commit db3c7a9f07a212d1774e6b432a08b231340e984d
|  Author: Ingo Molnar <mingo@elte•hu>
|  Date:   Tue May 13 15:37:05 2008 +0200

that commit was in intermediate testing phase in the 'scratch' branch, 
and a few days ago linux-next stopped picking up the scratch branch.

I've now cherry-picked this fix over into the rcu branch and everything 
should be fine again in the next linux-next iteration.

	Ingo

  reply	other threads:[~2008-05-22  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  5:59 linux-next: Tree for May 21 Stephen Rothwell
2008-05-21 11:32 ` [PATCH] linux-next: Tree for May 21 - build failure with netfilter on __nf_ct_helper_find() Kamalesh Babulal
2008-05-21 12:52   ` Stephen Rothwell
2008-05-21 13:29     ` Kamalesh Babulal
2008-05-22  0:11       ` Stephen Rothwell
2008-05-22  8:15         ` Ingo Molnar [this message]
2008-05-22 23:29           ` Stephen Rothwell

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=20080522081546.GB7222@elte.hu \
    --to=mingo@elte$(echo .)hu \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=apw@shadowen$(echo .)org \
    --cc=fbuihuu@gmail$(echo .)com \
    --cc=kamalesh@linux$(echo .)vnet.ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netfilter-devel@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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