public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst•de>
To: Artem Bityutskiy <Artem.Bityutskiy@nokia•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Christoph Hellwig <hch@lst•de>,
	linux-next@vger•kernel.org
Subject: Re: linux-next: ubifs tree build failure
Date: Tue, 12 Aug 2008 20:24:44 +0200	[thread overview]
Message-ID: <20080812182444.GB14420@lst.de> (raw)
In-Reply-To: <48A13DB8.4090003@nokia.com>

On Tue, Aug 12, 2008 at 10:37:28AM +0300, Artem Bityutskiy wrote:
> ext Stephen Rothwell wrote:
> >Hi Artem,
> >
> >Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> >fs/ubifs/super.c: In function 'ubifs_fh_to_dentry':
> >fs/ubifs/super.c:1611: error: implicit declaration of function 
> >'d_alloc_anon'
> >fs/ubifs/super.c:1611: warning: assignment makes pointer from integer 
> >without a cast
> >
> >Caused by interaction between commit
> >95b53e84e8899258a1af011a7216abb978afae26 ("kill d_alloc_anon") from the
> >vfs tree and b51e4badb0248ac75fe3128bb369d987e28b2f88 ("UBIFS: add NFS
> >support") from the ubifs tree.  The former removes d_alloc_anon and the
> >latter adds a new usage.
> >
> >For now, I have reverted the ubifs commit.  Christoph, maybe you could
> >provide a better solution.
> >
> >I have appended the reverted patch below.
> 
> I am not sure how to resolve things like this actually. I am planning to
> send ubifs-2.6.git upstream soon, so probably Christoph will be able to 
> amend
> his stuff after this. Or any other suggestion?

Please back this patch out, it's defintively not ready.

  parent reply	other threads:[~2008-08-12 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  6:24 linux-next: ubifs tree build failure Stephen Rothwell
2008-08-12  7:11 ` Artem Bityutskiy
2008-08-12  7:37 ` Artem Bityutskiy
2008-08-12  8:42   ` Stephen Rothwell
2008-08-12 18:24   ` Christoph Hellwig [this message]
2008-08-13  9:42     ` Artem Bityutskiy
2008-08-12 18:24 ` Christoph Hellwig
2008-08-12 21:39   ` Christoph Hellwig
2008-08-13  6:23     ` Artem Bityutskiy
2008-08-13  9:58     ` Artem Bityutskiy
2008-08-13 11:20       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-11-24  1:14 Stephen Rothwell
2009-11-24  6:31 ` Artem Bityutskiy
2009-11-24  7:28   ` 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=20080812182444.GB14420@lst.de \
    --to=hch@lst$(echo .)de \
    --cc=Artem.Bityutskiy@nokia$(echo .)com \
    --cc=linux-next@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