[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130906045722.GC28806@kroah.com>
Date: Thu, 5 Sep 2013 21:57:22 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@...el.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Rusty Russell <rusty@...tcorp.com.au>,
"Michael S. Tsirkin" <mst@...hat.com>,
Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-doc@...r.kernel.org, Asias He <asias@...hat.com>,
Nikhil Rao <nikhil.rao@...el.com>,
Ashutosh Dixit <ashutosh.dixit@...el.com>,
Caz Yokoyama <Caz.Yokoyama@...el.com>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@...el.com>,
Harshavardhan R Kharche <harshavardhan.r.kharche@...el.com>,
"Yaozu (Eddie) Dong" <eddie.dong@...el.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
Subject: Re: [PATCH RESEND v3 1/7] Intel MIC Host Driver for X100 family.
On Thu, Sep 05, 2013 at 04:41:31PM -0700, Sudeep Dutt wrote:
> drivers/misc/mic/common/mic_device.h | 37 +++
> drivers/misc/mic/host/mic_device.h | 109 +++++++++
Two different files, with the same name? You are asking for trouble in
the future, getting them confused :)
Please try to pick a unique name, especially when you later do things
like:
> +#include "../common/mic_device.h"
> +#include "mic_device.h"
Which just looks odd.
Again, not a big deal, follow-on patch can fix this.
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/
Powered by blists - more mailing lists