From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, Mel Gorman <mel@csn.ul.ie>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: Next 0205 build break : drivers/s390/block/dasd_proc.o
Date: Sat, 7 Feb 2009 00:06:36 +1100 [thread overview]
Message-ID: <20090207000636.ee67c759.sfr@canb.auug.org.au> (raw)
In-Reply-To: <498C03E1.1040204@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Fri, 06 Feb 2009 15:03:21 +0530 "Sachin P. Sant" <sachinp@in.ibm.com> wrote:
>
> Next 0205 defconfig build on s390x fails with :
>
> CC drivers/s390/block/dasd_proc.o
> drivers/s390/block/dasd_proc.c: In function dasd_proc_init:
> drivers/s390/block/dasd_proc.c:321: error: struct proc_dir_entry has no member named owner
> drivers/s390/block/dasd_proc.c:335: error: struct proc_dir_entry has no member named owner
> make[1]: *** [drivers/s390/block/dasd_proc.o] Error 1
> make: *** [drivers/s390/block/dasd_proc.o] Error 2
Looks like commit 4d38a69c6bc847828ae89c2249e82671ed4061c5 ("proc 2/2:
remove struct prioc_dir_entry::owner") from the proc tree missed at least
a couple.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-06 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 9:33 Next 0205 build break : drivers/s390/block/dasd_proc.o Sachin P. Sant
2009-02-06 13:06 ` Stephen Rothwell [this message]
2009-02-06 14:23 ` [Patch] Remove remaining ref to proc_dir_entry::owner Sachin P. Sant
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=20090207000636.ee67c759.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=adobriyan@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=sachinp@in.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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