From: "Denis V. Lunev" <den@openvz.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
jejb <James.Bottomley@HansenPartnership.com>,
gregkh <greg@kroah.com>, akpm <akpm@linux-foundation.org>,
sfr@canb.auug.org.au
Subject: Re: [PATCH -next 2/2] sysfs: sysfs_update_group stub for CONFIG_SYSFS=n
Date: Wed, 30 Apr 2008 14:58:21 +0400 [thread overview]
Message-ID: <1209553101.7357.2.camel@iris.sw.ru> (raw)
In-Reply-To: <20080423095622.25e29f45.randy.dunlap@oracle.com>
On Wed, 2008-04-23 at 09:56 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> scsi_transport_spi uses sysfs_update_group() when CONFIG_SYSFS=n,
> so provide a stub for it.
>
> next-20080423/drivers/scsi/scsi_transport_spi.c:1467: error: implicit declaration of function 'sysfs_update_group'
> make[3]: *** [drivers/scsi/scsi_transport_spi.o] Error 1
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
This patch seems lost. Current Linus GIT tree is still affected.
Regards,
Den
prev parent reply other threads:[~2008-04-30 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 16:56 [PATCH -next 2/2] sysfs: sysfs_update_group stub for CONFIG_SYSFS=n Randy Dunlap
2008-04-30 10:58 ` Denis V. Lunev [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=1209553101.7357.2.camel@iris.sw.ru \
--to=den@openvz.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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