From: Timur Tabi <timur@freescale.com>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: lseek() on entries in /proc/device-tree returns EINVAL
Date: Wed, 16 Apr 2008 16:16:04 -0500 [thread overview]
Message-ID: <48066C94.5040707@freescale.com> (raw)
In-Reply-To: <062801c8a006$a7715710$f6540530$@Tjernlund@transmode.se>
Joakim Tjernlund wrote:
> Good, bb should probably do the same. I just hope Al will allow a grace period and restore
> the old behavior so bb can catch up.
I don't see any reason why lseek() should not always work. Besides, a "grace
period" would mean that on some future kernel, older busybox will not work.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-04-16 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 20:57 lseek() on entries in /proc/device-tree returns EINVAL Timur Tabi
2008-04-16 21:01 ` Scott Wood
2008-04-16 21:09 ` Joakim Tjernlund
2008-04-16 21:10 ` Timur Tabi
2008-04-16 21:13 ` Joakim Tjernlund
2008-04-16 21:16 ` Timur Tabi [this message]
2008-04-16 21:40 ` Joakim Tjernlund
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=48066C94.5040707@freescale.com \
--to=timur@freescale.com \
--cc=Joakim.Tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).