public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: RE: [PATCH] OneNAND MTD support
Date: Mon, 11 Jul 2005 17:30:05 +0900	[thread overview]
Message-ID: <0IJG00C0MFM33V@mmp1.samsung.com> (raw)
In-Reply-To: <1121068041.26713.309.camel@tglx.tec.linutronix.de>

> 
> > > 
> > > +EXPORT_SYMBOL(onenand_scan);
> > > +EXPORT_SYMBOL(onenand_release);
> > > 
> > > Would you mind to change those exports to EXPORT_SYMBOL_GPL ?
> > 
> > In fact I not sure and also don't know license issue. 
> > If we develop the some commercial mtd user software then 
> can we use mtd
> > device code exported with GPL? Is there no problem?
> 
> User space software is not concerned of kernel licences.
> 
> If you talk about a proprietary closed source kernel module 
> which needs
> those exports, you are stepping into a legal grey area 
> regardless of the
> exports style. I don't see a point where it makes sense to 
> have a closed
> source board driver, as it just initializes a data structure and calls
> generic handling code. 
> 

OK
 
> 
> Some nitpicks though
> 
> +	/* The 10 msec is enough */
> +	timeout = jiffies + msecs_to_jiffies(10);
> +	while (time_before(jiffies, timeout)) {
> 
> On CPU's which have HZ=100 (1 jiffy == 10ms) this might be 
> critical, as
> you might set the timeout immidiately before the timer interrupt
> happens. Using a 20ms timeout will keep you on the safe side 
> in any case

No problem.

> 
> 
> Please clean up your includes to avoid redundant includes of header
> files.

which one do you mean?
Are there not required header file?


Regards

Kyungmin Park.

  reply	other threads:[~2005-07-11  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <940F0204B50E3E4886CC4E7D562F6D3448C212@dlee04.ent.ti.com>
2005-07-04  1:19 ` [PATCH] OneNAND MTD support Kyungmin Park
2005-07-04 10:05   ` Thomas Gleixner
2005-07-09  2:13     ` Kyungmin Park
2005-07-09  9:10       ` Thomas Gleixner
2005-07-11  1:53         ` Kyungmin Park
2005-07-11  7:47           ` Thomas Gleixner
2005-07-11  8:30             ` Kyungmin Park [this message]
2005-07-11  8:47               ` Thomas Gleixner
2005-07-11  9:23                 ` Kyungmin Park
2005-07-11 10:46                   ` Thomas Gleixner
2005-07-04 13:30   ` Artem B. Bityuckiy
2005-07-04 13:41     ` Thomas Gleixner
     [not found] <430D873B.1050108@in2soft.de>
2005-08-25 23:37 ` Kyungmin Park
2005-08-26  7:41   ` Bernhard Priewasser

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=0IJG00C0MFM33V@mmp1.samsung.com \
    --to=kyungmin.park@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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