[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1430447747.4545.3.camel@HansenPartnership.com>
Date: Thu, 30 Apr 2015 19:35:47 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux-kernel@...r.kernel.org,
Vinayak Holikatti <vinholikatti@...il.com>,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH 09/11] drivers/scsi: include <module.h> for modular
ufshcd-pltfrm code
On Thu, 2015-04-30 at 21:47 -0400, Paul Gortmaker wrote:
> This file is built off of a tristate Kconfig option and also contains
> modular function calls so it should explicitly include module.h to
> avoid compile breakage during header shuffles done in the future.
I don't understand your logic. The ufs code made a design choice to
consolidate most headers for the hcd code in a local include (ufshcd.h),
which includes module.h, so why would they explicitly need it here as
well? And if we follow your logic, why wouldn't they also need to
duplicate everything else (like the scsi includes)?
James
--
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