From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [PATCH v3 03/23] serial: omap: don't access the platform_device Date: Wed, 5 Sep 2012 13:27:21 -0700 Message-ID: <20120905202721.GA2430@kroah.com> References: <1345717983-18179-1-git-send-email-balbi@ti.com> <1345717983-18179-4-git-send-email-balbi@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1345717983-18179-4-git-send-email-balbi@ti.com> Sender: linux-kernel-owner@vger.kernel.org To: Felipe Balbi Cc: alan@linux.intel.com, Tony Lindgren , Kevin Hilman , Linux OMAP Mailing List , Linux ARM Kernel Mailing List , linux-serial@vger.kernel.org, Linux Kernel Mailing List , Santosh Shilimkar , Shubhrajyoti Datta , Sourav Poddar List-Id: linux-omap@vger.kernel.org On Thu, Aug 23, 2012 at 01:32:43PM +0300, Felipe Balbi wrote: > The driver doesn't need to know about its platform_device. > > Everything the driver needs can be done through the > struct device pointer. In case we need to use the > OMAP-specific PM function pointers, those can make > sure to find the device's platform_device pointer > so they can find the struct omap_device through > pdev->archdata field. > > Tested-by: Shubhrajyoti D > Acked-by: Santosh Shilimkar > Signed-off-by: Felipe Balbi > Acked-by: Tony Lindgren This series fails when applying to my tty-next branch at this patch :( Care to refresh it, and resend it, with Tony's acks added, so I can apply it? Note, I've already applied the first two. thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Wed, 5 Sep 2012 13:27:21 -0700 Subject: [PATCH v3 03/23] serial: omap: don't access the platform_device In-Reply-To: <1345717983-18179-4-git-send-email-balbi@ti.com> References: <1345717983-18179-1-git-send-email-balbi@ti.com> <1345717983-18179-4-git-send-email-balbi@ti.com> Message-ID: <20120905202721.GA2430@kroah.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Aug 23, 2012 at 01:32:43PM +0300, Felipe Balbi wrote: > The driver doesn't need to know about its platform_device. > > Everything the driver needs can be done through the > struct device pointer. In case we need to use the > OMAP-specific PM function pointers, those can make > sure to find the device's platform_device pointer > so they can find the struct omap_device through > pdev->archdata field. > > Tested-by: Shubhrajyoti D > Acked-by: Santosh Shilimkar > Signed-off-by: Felipe Balbi > Acked-by: Tony Lindgren This series fails when applying to my tty-next branch at this patch :( Care to refresh it, and resend it, with Tony's acks added, so I can apply it? Note, I've already applied the first two. thanks, greg k-h