On Thu, Oct 05, 2017 at 11:41:38AM +0300, Kalle Valo wrote: > Himanshu Jha <himanshujha199640@xxxxxxxxx> writes: > > >> > --- a/drivers/net/wireless/marvell/mwifiex/cmdevt.c > >> > +++ b/drivers/net/wireless/marvell/mwifiex/cmdevt.c > >> > @@ -17,6 +17,7 @@ > >> > * this warranty disclaimer. > >> > */ > >> > > >> > +#include <linux/unaligned/access_ok.h> > >> > >> I don't think this is correct. Should it be asm/unaligned.h? > > > > Would mind explainig me as to why it is incorrect! Also, it defined in > > both the header files but, why is asm/unaligned.h preferred ? > > asm/unaligned.h seems to be the toplevel header file which includes > header files based on arch configuration. Also grepping the sources > support that, nobody from drivers/ include access_ok.h directly. > Yes, you are correct! I will send v2 patch with asm/unaligned.h > But I can't say that I fully understand how the header files work so > please do correct me if I have mistaken. > It is confusing to me as well. There are various instances where a function used in file say for eg int func_align (void* a) is used and it is defined in align.h But many files don't *directly* include align.h and rather include any other header which includes align.h Is compiling the file the only way to check if apppropriate header is included or is there some other way to check for it. Thanks
