[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YcF9rRTVzrbCyOtq@kroah.com>
Date: Tue, 21 Dec 2021 08:09:33 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Mike Ximing Chen <mike.ximing.chen@...el.com>
Cc: linux-kernel@...r.kernel.org, arnd@...db.de,
dan.j.williams@...el.com, pierre-louis.bossart@...ux.intel.com,
netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org
Subject: Re: [RFC PATCH v12 00/17] dlb: introduce DLB device driver
On Tue, Dec 21, 2021 at 12:50:30AM -0600, Mike Ximing Chen wrote:
> v12:
<snip>
How is a "RFC" series on version 12? "RFC" means "I do not think this
should be merged, please give me some comments on how this is all
structured" which I think is not the case here.
> - The following coding style changes suggested by Dan will be implemented
> in the next revision
> -- Replace DLB_CSR_RD() and DLB_CSR_WR() with direct ioread32() and
> iowrite32() call.
> -- Remove bitmap wrappers and use linux bitmap functions directly.
> -- Use trace_event in configfs attribute file update.
Why submit a patch series that you know will be changed? Just do the
work, don't ask anyone to review stuff you know is incorrect, that just
wastes our time and ensures that we never want to review it again.
greg k-h
Powered by blists - more mailing lists