public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.27-rc6-mmotm0913 build error - fs-sysfs-dirc-remove-unused-__sysfs_get_dentry.patch
Date: Mon, 15 Sep 2008 11:15:08 -0700	[thread overview]
Message-ID: <m17i9dgtsj.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <48256.1221495403@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Mon, 15 Sep 2008 12:16:43 -0400")

Valdis.Kletnieks@vt.edu writes:

> Trying to build 2.6.27-rc6-mmotm0913 dies a horrid death:
>
>   CC      fs/sysfs/dir.o
> fs/sysfs/dir.c: In function sysfs_mv_dir:
> fs/sysfs/dir.c:993: error: implicit declaration of function
> __sysfs_get_dentry
> fs/sysfs/dir.c:993: warning: assignment makes pointer from integer without a
> cast
> make[2]: *** [fs/sysfs/dir.o] Error 1
> make[1]: *** [fs/sysfs] Error 2
> make: *** [fs] Error 2
>
>
> Diagnosis: Andrew added fs-sysfs-dirc-remove-unused-__sysfs_get_dentry.patch,
> but somebody (Eric? was touching a lot of sysfs) in linux-next.patch added a
> new user in sysfs_mv_dir.

Thanks that is a very helpful diagnosis.

> Looks like people need to get on the same page about that patch?

Greg stopped halfway through merging my patchset earlier, so I'm
guessing that is why __sysfs_get_dentry looked unused.  

As seen above I really did use that function ;) So a patch
to remove it is the wrong thing.

Eric

      reply	other threads:[~2008-09-15 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-15 16:16 2.6.27-rc6-mmotm0913 build error - fs-sysfs-dirc-remove-unused-__sysfs_get_dentry.patch Valdis.Kletnieks
2008-09-15 18:15 ` Eric W. Biederman [this message]

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=m17i9dgtsj.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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