All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: "s.rawat" <imsaurabhrawat@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Regarding generic_buffer.c Application for Android
Date: Mon, 13 Apr 2015 07:26:52 +0100	[thread overview]
Message-ID: <B74F5E0D-FE1C-422F-9D2E-985137E684E7@jic23.retrosnub.co.uk> (raw)
In-Reply-To: <CALwa49us7JVeYYga7fJxMx0=EbyLMuaAASGhU8=9AWYV2u96uQ@mail.gmail.com>



On 13 April 2015 04:40:17 BST, "s.rawat" <imsaurabhrawat@gmail.com> wrote:
>On Fri, Apr 10, 2015 at 11:49 AM, Jonathan Cameron <jic23@kernel.org>
>wrote:
>> Hit google
>> http://pubs.opengroup.org/onlinepubs/009695399/functions/seekdir.html
>> So for POSIX compliance they are optional.
>
>You mean seekdir(dp, 0); in function inline int
>build_channel_array(...) is optional?If I comment it, will it have no
>effect? This function is called inside main() of generic_buffer.c and
>I cant get it compiled with the tool chain I have.Is there any
>alternate code I can replace it with if it is Not Optional?
The functionality is not optional. There is no obligation for the operating system to implement seekdir.

Here equivalent is probably to close and reopen the directory.
>
>I can take care of le16toh/be16toh.
>
>Thanks and Rgds,
>S

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2015-04-13  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALwa49vRGN_VaJ147PVF8Cf+8vnBotWVh7hmxLj=jaAba5QTTw@mail.gmail.com>
2015-04-09 17:56 ` Regarding generic_buffer.c Application for Android Jonathan Cameron
2015-04-10  4:18   ` s.rawat
2015-04-10  6:19     ` Jonathan Cameron
2015-04-13  3:40       ` s.rawat
2015-04-13  6:26         ` Jonathan Cameron [this message]
2015-04-13  9:49           ` s.rawat
2015-04-13  9:51           ` s.rawat
2015-04-13 10:05           ` s.rawat
2015-04-20 10:34             ` s.rawat
2015-06-09  4:09               ` s.rawat

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=B74F5E0D-FE1C-422F-9D2E-985137E684E7@jic23.retrosnub.co.uk \
    --to=jic23@jic23.retrosnub.co.uk \
    --cc=imsaurabhrawat@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.