mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Subhasish Ghosh <subhasish@mistralsolutions.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	linux-arm-kernel@lists.infradead.org,
	davinci-linux-open-source@linux.davincidsp.com,
	sachi@mistralsolutions.com, Samuel Ortiz <sameo@linux.intel.com>,
	open list <linux-kernel@vger.kernel.org>,
	"Watkins, Melissa" <m-watkins@ti.com>
Subject: Re: [PATCH v4 01/11] mfd: add pruss mfd driver
Date: Tue, 24 May 2011 06:43:38 -0700	[thread overview]
Message-ID: <20110524134338.GA13491@kroah.com> (raw)
In-Reply-To: <201105241440.34854.arnd@arndb.de>

On Tue, May 24, 2011 at 02:40:34PM +0200, Arnd Bergmann wrote:
> On Tuesday 24 May 2011, Subhasish Ghosh wrote:
> > Would it be a good approach to first get a basic sensible
> > driver into the tree and then work towards improving and
> > adjusting for future compatibilities.
> 
> The main problem with that is that you cannot really change
> user-visible interfaces after the driver is merged. Anything
> regarding sysfs attributes and firmware file contents needs
> to be fixed. You can however still change in-kernel interfaces
> at a later point without problems.
> 
> > That way we can gradually build towards the perfect driver
> > in steps, rather than digressing far too off suddenly.
> > That would be some source of motivation for me too.
> 
> You can definitely add the driver to drivers/staging/pruss/,
> as the rules for staging drivers are different. I think that
> would indeed be helpful at this point. As soon as all
> interfaces have stabilized, you can then move the individual
> parts to their final location.
> 
> Greg maintains the staging drivers, and he can surely point
> you to a document describing what is required for a driver.

There really are only 3 rules:
	- proper license
	- self-contained in a drivers/staging/DRIVER_NAME/ directory
	- must properly build

> Mainly, this includes having a patch that adds a single
> directory with all the driver files under drivers/staging.
> The driver must be able to compile without errors and you need
> a TODO file listing the remaining issues that prevent you
> from having a non-staging driver.

Ah, forgot the TODO on the list of rules, I'll have to add that next
time.

Someone feel free to send me a patch :)

thanks,

greg k-h

  reply	other threads:[~2011-05-24 13:43 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1303474109-6212-1-git-send-email-subhasish@mistralsolutions.com>
2011-04-22 12:08 ` Subhasish Ghosh
2011-04-22 16:00   ` Marc Kleine-Budde
2011-04-27  6:39     ` Subhasish Ghosh
2011-04-27  7:29       ` Marc Kleine-Budde
2011-04-27  9:12         ` Russell King - ARM Linux
2011-04-27 13:18           ` Subhasish Ghosh
2011-04-27 13:35             ` Marc Kleine-Budde
2011-04-28  7:22               ` Subhasish Ghosh
2011-04-28  7:46                 ` Arnd Bergmann
2011-04-27 13:16   ` Arnd Bergmann
2011-04-27 13:38     ` Subhasish Ghosh
2011-04-27 14:05       ` Arnd Bergmann
2011-04-28  7:17         ` Subhasish Ghosh
2011-04-28  7:35           ` Arnd Bergmann
2011-05-04  7:18             ` Subhasish Ghosh
2011-05-04 13:44               ` Arnd Bergmann
2011-05-04 14:38               ` Nori, Sekhar
2011-05-05 13:25                 ` Subhasish Ghosh
2011-05-05 14:12                   ` Arnd Bergmann
2011-05-10  9:53                     ` Subhasish Ghosh
2011-05-10 21:44                       ` Arnd Bergmann
2011-05-11  9:28                         ` Subhasish Ghosh
2011-05-11 20:03                           ` Arnd Bergmann
2011-05-13 10:55                             ` Subhasish Ghosh
2011-05-14 16:01                               ` Mark Brown
2011-05-14 20:33                                 ` Arnd Bergmann
2011-05-14 22:14                                   ` Mark Brown
2011-05-15  9:33                                     ` Arnd Bergmann
2011-05-16  6:06                                       ` Subhasish Ghosh
2011-05-23 15:30                                         ` Arnd Bergmann
2011-05-24 12:17                                           ` Subhasish Ghosh
2011-05-24 12:40                                             ` Arnd Bergmann
2011-05-24 13:43                                               ` Greg KH [this message]
2011-05-30 13:25                                                 ` Subhasish Ghosh
2011-05-30 14:02                                                   ` Greg KH
2011-05-30 14:38                                                     ` Subhasish Ghosh
2011-05-30 14:04                                                   ` Arnd Bergmann
2011-05-30 14:13                                                     ` Subhasish Ghosh
2011-05-30 14:43                                                       ` Arnd Bergmann
2011-05-30 15:28                                                         ` Subhasish Ghosh
2011-05-22 20:24                                   ` Samuel Ortiz
2011-05-22 20:21                             ` Samuel Ortiz
2011-05-23 15:13                               ` Arnd Bergmann
2011-04-22 12:08 ` [PATCH v4 02/11] da850: add pruss clock Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 03/11] da850: pruss platform specific additions Subhasish Ghosh
2011-04-26 11:06   ` Sergei Shtylyov
2011-04-27  6:43     ` Subhasish Ghosh
2011-04-27 10:05       ` Sergei Shtylyov
2011-04-27 10:19         ` Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 04/11] da850: pruss board " Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 05/11] mfd: pruss SUART private data Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 06/11] da850: pruss SUART board specific additions Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 07/11] da850: pruss SUART platform " Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 08/11] tty: add pruss SUART driver Subhasish Ghosh
2011-04-25 21:20   ` Greg KH
2011-04-26  6:51     ` Nori, Sekhar
2011-04-26 12:45       ` Greg KH
2011-04-27  5:23         ` Subhasish Ghosh
2011-04-27 11:19           ` Nori, Sekhar
2011-04-27 13:15             ` Subhasish Ghosh
2011-04-27 17:50               ` Nori, Sekhar
2011-05-02  8:34                 ` Subhasish Ghosh
2011-05-02 17:15                   ` Nori, Sekhar
2011-05-10 10:54             ` Subhasish Ghosh
2011-05-10 13:13               ` Nori, Sekhar
2011-05-13 12:10                 ` Subhasish Ghosh
2011-05-09 13:39   ` Subhasish Ghosh
2011-05-09 13:46     ` Alan Cox
2011-05-09 13:50       ` Subhasish Ghosh
2011-05-09 13:55         ` Alan Cox
2011-05-10  6:17           ` Subhasish Ghosh
2011-05-10 13:32             ` Alan Cox
2011-05-11  7:01               ` Subhasish Ghosh
2011-05-11 10:35                 ` Alan Cox
2011-04-22 12:08 ` [PATCH v4 09/11] mfd: pruss CAN private data Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 10/11] da850: pruss CAN platform specific additions Subhasish Ghosh
2011-04-22 12:08 ` [PATCH v4 11/11] da850: pruss CAN board " Subhasish Ghosh
2011-04-22 16:03   ` Marc Kleine-Budde
2011-04-26 10:57   ` Sergei Shtylyov
2011-04-27  7:03     ` Subhasish Ghosh
2011-05-20  5:38 [PATCH v4 01/11] mfd: add pruss mfd driver Subhasish Ghosh

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=20110524134338.GA13491@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-watkins@ti.com \
    --cc=nsekhar@ti.com \
    --cc=sachi@mistralsolutions.com \
    --cc=sameo@linux.intel.com \
    --cc=subhasish@mistralsolutions.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

Powered by JetHome