Date: Wed, 11 Aug 2010 08:15:10 -0700
From: Greg KH <gregkh@suse.de>
To: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Cc: meego-dev@meego.com, LKML <linux-kernel@vger.kernel.org>,
        qi.wang@intel.com, yong.y.wang@intel.com,
        andrew.chih.howe.khor@intel.com, arjan@linux.intel.com
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_IEEE1588 driver to
 2.6.35
Message-ID: <20100811151510.GB9180@suse.de>
References: <4C612AA4.5040100@dsn.okisemi.com>
 <20100810171343.GE21220@suse.de>
 <002601cb3926$edaf24d0$66f8800a@maildom.okisemi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002601cb3926$edaf24d0$66f8800a@maildom.okisemi.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 860
Lines: 30

On Wed, Aug 11, 2010 at 04:29:25PM +0900, Masayuki Ohtake wrote:
> Hi Greg,
> 
> > Do they all have to be ioctls?  What exactly are they doing?
> I think using ioctl is common for this patch.

"Common" is not ok, right?

> Do you think that using ioctl is NOT appropriate for this patch?

Yes.

> Let me know your intension in more detail.

Please express yours.  Why do you feel you need these to be ioctls?
What exactly are they doing?  Where is the documentation for them all?

> > And are they 32/64bit safe?
> Only 32bit support.

That's an obvious problem that needs to be resolved, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/