From: Arnd Bergmann <arnd@arndb.de>
To: Amit Shah <amit.shah@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: manual merge of the bkl-llseek tree with the rr tree
Date: Thu, 16 Sep 2010 10:20:01 +0200 [thread overview]
Message-ID: <201009161020.01392.arnd@arndb.de> (raw)
In-Reply-To: <20100916065438.GE2429@amit-laptop.redhat.com>
On Thursday 16 September 2010 08:54:39 Amit Shah wrote:
> Arnd, the device is supposed to be non-seekable so I'll add a
> nonseekable_open() to the open() call.
>
> So I guess the llseek operation should ne no_llseek instead of
> noop_llseek. Will you change that in your patchset? Should I do that
> in the patch I'll queue up?
Yes, I think it's best if you just do both changes in your patch, I'll
drop this file from my series then.
Any driver that we can make use no_llseek instead of noop_llseek
is a step forward.
Arnd
next prev parent reply other threads:[~2010-09-16 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 3:26 linux-next: manual merge of the bkl-llseek tree with the rr tree Stephen Rothwell
2010-09-16 6:54 ` Amit Shah
2010-09-16 8:20 ` Arnd Bergmann [this message]
2010-09-16 8:56 ` Amit Shah
2010-09-26 14:52 ` Arnd Bergmann
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=201009161020.01392.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=amit.shah@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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