The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: eshwar <eshwar@moschip.com>
Cc: Raj <inguva@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Write USB Device Driver entry not called
Date: Wed, 13 Oct 2004 11:37:59 +0100	[thread overview]
Message-ID: <1097663878.4440.0.camel@localhost.localdomain> (raw)
In-Reply-To: <001401c4b796$abcddfb0$41c8a8c0@Eshwar>

On Iau, 2004-10-21 at 18:52, eshwar wrote:
> Open is sucessfull.... I don't think the problem the flags of open

I do. See any book on C/Unix style file opening. For an existing file
you want
		open("foo", O_flags)

for a new file possibly

		open("foo", O_CREAT|o_flags, S_Iblah)



  parent reply	other threads:[~2004-10-13 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 11:44 Write USB Device Driver entry not called eshwar
2004-10-13  6:15 ` Raj
2004-10-21 17:52   ` eshwar
2004-10-13  6:38     ` Raj
2004-10-13 10:37     ` Alan Cox [this message]
2004-10-23  1:42       ` eshwar
2004-10-14  3:39         ` Raj
2004-10-21  3:54           ` eshwar
2004-10-14  4:19             ` Raj

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=1097663878.4440.0.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=eshwar@moschip.com \
    --cc=inguva@gmail.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