[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45A0E7B350CB4DF685D18EFE6EB1CB76@subhasishg>
Date: Mon, 30 May 2011 18:55:12 +0530
From: "Subhasish Ghosh" <subhasish@...tralsolutions.com>
To: "Greg KH" <greg@...ah.com>, "Arnd Bergmann" <arnd@...db.de>
Cc: "Mark Brown" <broonie@...nsource.wolfsonmicro.com>,
"Nori, Sekhar" <nsekhar@...com>,
<linux-arm-kernel@...ts.infradead.org>,
<davinci-linux-open-source@...ux.davincidsp.com>,
<sachi@...tralsolutions.com>,
"Samuel Ortiz" <sameo@...ux.intel.com>,
"open list" <linux-kernel@...r.kernel.org>,
"Watkins, Melissa" <m-watkins@...com>
Subject: Re: [PATCH v4 01/11] mfd: add pruss mfd driver
Greg,
> 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.
>
How do I handle the headers. I have two header files in the
include/linux/mfd.
Should I submit them as a separate patch into mfd.
These headers are also used by pruss uart implementation.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists