public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Morinaga" <morinaga526@dsn.okisemi.com>,
	<margie.foster@intel.com>, <alan@linux.intel.com>,
	<arjan@linux.intel.com>, <andrew.chih.howe.khor@intel.com>,
	<qi.wang@intel.com>, <yong.y.wang@intel.com>,
	"LKML" <linux-kernel@vger.kernel.org>, <meego-dev@meego.com>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35
Date: Mon, 23 Aug 2010 21:30:51 +0900	[thread overview]
Message-ID: <000401cb42bf$07e201f0$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 20100819152214.GD2562@suse.de

----- Original Message ----- 
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>; <yong.y.wang@intel.com>; <qi.wang@intel.com>;
<andrew.chih.howe.khor@intel.com>; <arjan@linux.intel.com>; <alan@linux.intel.com>; <margie.foster@intel.com>;
"Morinaga" <morinaga526@dsn.okisemi.com>
Sent: Friday, August 20, 2010 12:22 AM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35


> On Thu, Aug 19, 2010 at 09:25:03PM +0900, Masayuki Ohtake wrote:
> > Please find <MASA>
>
> If someone takes the time to review your code and ask questions, it is
> considered common courtesy to at least answer them all and not ignore
> some of them.  Please do so.
>
> > > >  drivers/misc/Kconfig    |    9 +
> > > >  drivers/misc/Makefile   |    1 +
> > > >  drivers/misc/pch_phub.c |  722 +++++++++++++++++++++++++++++++++++++++++++++++
> > > >  3 files changed, 732 insertions(+), 0 deletions(-)
> > > >  create mode 100755 drivers/misc/pch_phub.c
> > >
> > > You forgot to add documentation for your sysfs files in
> > > Documentation/ABI/ which is a requiremend when you add new ones.
> >
> > <MASA>
> > Which folder should we put stable/ or testing/ ?
>
> Which do you feel it should be in?
I think 'testing' is appropriate.

>
> > > > +};
> > > > +
> > > > +/* SROM SPEC for MAC address assignment offset */
> > > > +static const int pch_phub_mac_offset[ETH_ALEN] = {0x3, 0x2, 0x1, 0x0, 0xb, 0xa};
> > > > +
> > > > +static DEFINE_MUTEX(pch_phub_mutex);
> > > > +static struct pch_phub_reg pch_phub_reg;
> > >
> > > So you can only have one of these devices in a system at the same time?
> > > What happens when a machine ships with two of them?
> >
> > <MASA>
> > I can't understand the above questioin meaning.
> > Give me more information, please.
> > What's does the above "these devices" mean?
>
> The device the driver is controlling.  What happens when this driver
> runs on a system that has 2 of these devices?  You need to be able to
> handle multiple devices, and that doesn't happen with a single variable,
> right?  Please dynamically allocate it and make the lock associated to
> the actual device, not the whole driver, if possible.
I can understand your saying.
But our driver for Topcliff doesn't support multiple device but single device only.
>From LSI structure point of view, I think, it is impossible that topcliff is used as multiple devices.
None the less, should our driver support multiple device ?

Thanks, Ohtake(OKISEMI)



  reply	other threads:[~2010-08-23 12:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18  9:10 [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35 Masayuki Ohtak
2010-08-18 13:14 ` Greg KH
2010-08-19  6:27   ` Masayuki Ohtake
2010-08-19 15:17     ` Greg KH
2010-08-20  6:53       ` Masayuki Ohtake
2010-08-19 12:25   ` Masayuki Ohtake
2010-08-19 15:22     ` Greg KH
2010-08-23 12:30       ` Masayuki Ohtake [this message]
2010-08-23 15:34         ` Greg KH
2010-08-24  0:02           ` Masayuki Ohtake
2010-08-24  6:46   ` Masayuki Ohtake
  -- strict thread matches above, loose matches on Subject: below --
2010-08-24  6:47 Masayuki Ohtak
2010-08-24 13:22 ` Greg KH
2010-08-25 10:16 Masayuki Ohtak
2010-08-25 12:05 Masayuki Ohtak
2010-09-01 12:16 Masayuki Ohtak
2010-09-01 23:09 ` Greg KH
2010-09-01 23:58   ` Masayuki Ohtake
2010-09-02  0:59     ` Greg KH
2010-09-02  1:02 ` Greg KH
2010-09-02  2:36   ` Masayuki Ohtake
2010-09-02  3:22     ` Greg KH
2010-09-02  3:29       ` Wang, Qi
2010-09-02  6:44         ` Masayuki Ohtake
2010-09-02 13:19           ` Greg KH
2010-09-03  0:22             ` Masayuki Ohtake
2010-09-03  2:14               ` Greg KH
2010-09-03  1:13             ` Wang, Qi
2010-09-02  6:38       ` Masayuki Ohtake
2010-09-02 13:18         ` Greg KH
2010-09-03  0:17           ` Masayuki Ohtake

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='000401cb42bf$07e201f0$66f8800a@maildom.okisemi.com' \
    --to=masa-korg@dsn.okisemi.com \
    --cc=alan@linux.intel.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margie.foster@intel.com \
    --cc=meego-dev@meego.com \
    --cc=morinaga526@dsn.okisemi.com \
    --cc=qi.wang@intel.com \
    --cc=yong.y.wang@intel.com \
    /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