linux-kernel - RE: [PATCH] drivers:staging:ti-st: remove st_get_plat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19F8576C6E063C45BE387C64729E7394046836CE5C@dbde02.ent.ti.com>
Date:	Wed, 1 Sep 2010 03:53:19 +0530
From:	"Savoy, Pavan" <pavan_savoy@...com>
To:	Greg KH <gregkh@...e.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: RE: [PATCH] drivers:staging:ti-st: remove st_get_plat_device


Greg,

> -----Original Message-----
> From: Greg KH [mailto:gregkh@...e.de]
> Sent: Monday, August 30, 2010 11:11 PM
> To: Savoy, Pavan
> Cc: linux-kernel@...r.kernel.org; devel@...verdev.osuosl.org
> Subject: Re: [PATCH] drivers:staging:ti-st: remove st_get_plat_device
> 
> On Tue, Aug 31, 2010 at 03:39:00AM +0530, Savoy, Pavan wrote:
> > Greg,
> >
> >
> >
> > > -----Original Message-----
> > > From: Greg KH [mailto:gregkh@...e.de]
> > > Sent: Saturday, August 21, 2010 10:33 PM
> > > To: Savoy, Pavan
> > > Cc: Randy Dunlap; alan@...rguk.ukuu.org.uk; linux-kernel@...r.kernel.org;
> > > devel@...verdev.osuosl.org; Jain, Naveen
> > > Subject: Re: [PATCH] drivers:staging:ti-st: remove st_get_plat_device
> > >
> > > On Sun, Aug 22, 2010 at 07:20:00AM +0530, Pavan Savoy wrote:
> > > > Greg,
> > > >
> > > > On Thu, Aug 19, 2010 at 11:07 PM, Randy Dunlap <randy.dunlap@...cle.com>
> > > wrote:
> > > > > On 08/19/10 10:35, Savoy, Pavan wrote:
> > > > >> Randy,
> > > > >>
> > > > >>
> > > > >>> -----Original Message-----
> > > > >>> From: Randy Dunlap [mailto:randy.dunlap@...cle.com]
> > > > >>> Sent: Thursday, August 19, 2010 12:32 PM
> > > > >>> To: Savoy, Pavan
> > > > >>> Cc: gregkh@...e.de; alan@...rguk.ukuu.org.uk; linux-
> > > kernel@...r.kernel.org;
> > > > >>> devel@...verdev.osuosl.org; Jain, Naveen
> > > > >>> Subject: Re: [PATCH] drivers:staging:ti-st: remove
> st_get_plat_device
> > > > >>>
> > > > >>> On 08/19/10 11:08, pavan_savoy@...com wrote:
> > > > >>>> From: Pavan Savoy <pavan_savoy@...com>
> > > > >>>>
> > > > >>>> In order to support multiple ST platform devices, a new symbol
> > > > >>>> 'st_get_plat_device' earlier needed to be exported by the
> arch/XX/brd-
> > > XX.c
> > > > >>>> file which intends to add the ST platform device.
> > > > >>>>
> > > > >>>> On removing this dependency, now inside ST driver maintain the
> array of
> > > > >>>> ST platform devices that would be registered.
> > > > >>>> As of now let id=0, as and when we end up having such platforms
> > > > >>>> where mutliple ST devices can exist, id would come from
> > > > >>>> protocol drivers (BT, FM and GPS) as to on which platform device
> > > > >>>> they want to register to.
> > > > >>>>
> > > > >>>> Signed-off-by: Pavan Savoy <pavan_savoy@...com>
> > > > >>>
> > > > >>> Thanks, that builds cleanly. ??I'm OK with it if you are comfortable
> > > with a
> > > > >>> hard limit on the fixed number of devices that can be supported:
> > > > >>
> > > > >> Yep, Thanks for pointing out, sort of cleaned up the code.
> > > > >>
> > > > >>> +#define MAX_ST_DEVICES ?? ?? ??3 ?? ?? ?? /* Imagine 1 on each UART
> for
> > > now */
> > > > >>> +struct platform_device *st_kim_devices[MAX_ST_DEVICES];
> > > > >>>
> > > > >>> We usually try not to have such limits nor use arrays like that,
> > > > >>> but if the nature of the device and its platform/environment is like
> > > > >>> that, so be it.
> > > > >>>
> > > > >>
> > > > >> Actually on all platforms that I have seen there's only 1 such
> device.
> > > > >> The device is basically a connectivity chip (with Bluetooth, FM and
> GPS
> > > working
> > > > >> on a single UART)
> > > > >>
> > > > >> The number which I mentioned was out of imagination.
> > > > >> I don't think we are ever going to have multiple of them either...
> > > > >
> > > > > OK, thanks.
> > > > >
> > > > > Acked-by: Randy Dunlap <randy.dunlap@...cle.com>
> > > >
> > > >
> > > > Can you please merge this patch ? Also please have a look at the driver
> and
> > > > suggest what needs to be done to move it out of staging.
> > >
> > > Yes, I will work on it, sorry, been swamped with other work lately.
> > >
> > > Don't worry, this patch is in my "to-apply" queue.
> >
> > Any update on this?
> 
> Nope, sorry.  I got sick and combined with vacation requirements from
> the family, and my "real job" and other things lately, I hope to get to
> it by the end of this week.  If not, kick me, I'll have time on a
> trans-continent flight next week that should give me plenty of time to
> do this...

Gzee Thanks, so since you added the patch now, I guess you will be reviewing
The ti-st driver and sketch out plans to move it out of staging on your long trans-Continent flight?


> thanks,
> 
> greg k-h
--
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/