From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: make new character devices nonseekable
Date: Sun, 26 Sep 2010 18:22:55 -0700 [thread overview]
Message-ID: <20100927012255.GA16490@kroah.com> (raw)
In-Reply-To: <201009261731.53062.arnd@arndb.de>
On Sun, Sep 26, 2010 at 05:31:52PM +0200, Arnd Bergmann wrote:
> As a preparation for changing the default behaviour of llseek to no_llseek,
> every file_operations structure should have a .llseek operation.
>
> There are three new instances in staging now, which can all be changed
> into no_llseek explicitly since the devices do not need to seek.
>
> Add nonseekable_open where appropriate, to prevent pread/pwrite as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> bcm/Bcmchar.c | 3 +++
> bcm/InterfaceInit.c | 1 +
> ft1000/ft1000-usb/ft1000_chdev.c | 2 ++
> 3 files changed, 6 insertions(+)
Odd, this patch breaks the build, what's up?
Hm, do I need to apply it to a recent Linus version? My staging-next
tree is 2.6.36-rc2 based, do I need to update it?
thanks,
greg k-h
prev parent reply other threads:[~2010-09-27 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 15:31 [PATCH] staging: make new character devices nonseekable Arnd Bergmann
2010-09-27 1:22 ` Greg KH [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=20100927012255.GA16490@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--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