From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: Peng Tao <bergwolf@gmail.com>, Kent Overstreet <koverstreet@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: next-20130805 - compile errors in drivers/staging/lustre/lustre/llite/file.c
Date: Mon, 05 Aug 2013 12:20:06 -0400 [thread overview]
Message-ID: <6501.1375719606@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
Not sure how this train wreck happened - 'git log' shows the last patch to
touch include/linux/aio.h was some stuff of Kent's back in May, and 'git blame'
says the 2 lines of code that died were added on 2013-05-02.
It compiled when I build next-0730.
And yet, this morning, I get this building -0805:
CC [M] drivers/staging/lustre/lustre/llite/file.o
drivers/staging/lustre/lustre/llite/file.c: In function 'll_file_read':
drivers/staging/lustre/lustre/llite/file.c:1012:7: error: 'struct kiocb' has no member named 'ki_left'
kiocb->ki_left = count;
^
drivers/staging/lustre/lustre/llite/file.c: In function 'll_file_write':
drivers/staging/lustre/lustre/llite/file.c:1071:7: error: 'struct kiocb' has no member named 'ki_left'
kiocb->ki_left = count;
^
make[5]: *** [drivers/staging/lustre/lustre/llite/file.o] Error 1
Any ideas? Only thing I can think of is that Kent's stuff went into some
tree in May, but only surfaced in linux-next in the last little bit...
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next reply other threads:[~2013-08-05 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 16:20 Valdis Kletnieks [this message]
2013-08-06 10:12 ` Peng Tao
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=6501.1375719606@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bergwolf@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=koverstreet@google.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
all inboxes | Powered by JetHome®