From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Mon, 7 Mar 2016 12:15:34 -0800
Subject: Driver duplicate?
In-Reply-To: <CAK7rcp8Zj=sycmewFBgf8rOdC+YLY+qY8j6EQsP0a8OL=1d-aA@mail.gmail.com>
References: <CAK7rcp9ZmbaHOhxmCSSQxkDtA6i=QMwhXgwcKZ1JwN3=JQmnvQ@mail.gmail.com>
	<CAK7rcp8Zj=sycmewFBgf8rOdC+YLY+qY8j6EQsP0a8OL=1d-aA@mail.gmail.com>
Message-ID: <20160307201534.GB26401@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, Mar 07, 2016 at 03:05:41PM -0500, Kenneth Adam Miller wrote:
> Actually, I just realized that there is probably a way to look up the character
> device name with the file* that is passed in with the mmap call. Can anybody
> say how?

Why not just use the "normal" way to do this?  Have you tried it and it
somehow failed?

There are at least 3 different ways to do this, depending on your driver
code structure, so I can't give you a straight "do it this way" type
answer, sorry.

greg k-h