[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YG9HDbMu3EbS3ekW@kroah.com>
Date: Thu, 8 Apr 2021 20:10:21 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Min Li <min.li.xe@...esas.com>
Cc: "derek.kiernan@...inx.com" <derek.kiernan@...inx.com>,
"dragan.cvetic@...inx.com" <dragan.cvetic@...inx.com>,
"arnd@...db.de" <arnd@...db.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v3 2/2] misc: Add Renesas Synchronization
Management Unit (SMU) support
On Thu, Apr 08, 2021 at 06:01:42PM +0000, Min Li wrote:
> >
> > That does not make sense, this is only one kernel module, with one .h file in
> > this patch, I do not see those other files you are talking about...
> >
> > And if you have named registers that are identical, and yet you only work on
> > one device, that feels like a design flaw somewhere :)
> >
>
> Hi Greg, the register files are in the 1/2 patch for the mfd part of the change.
> The reason they have same named register is because they are all synchronization
> devices and they share some similar features
But what does that have to do with the misc device?
totally confused,
greg k-h
Powered by blists - more mailing lists