[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAALAos8dcW8k0D1pvHMXF6MuQU7PecdzW_t1DvG8LQ8urvusWA@mail.gmail.com>
Date: Thu, 20 Jul 2017 09:35:57 +0530
From: Anup Patel <anup.patel@...adcom.com>
To: Scott Branden <scott.branden@...adcom.com>
Cc: Will Deacon <will.deacon@....com>,
Robin Murphy <robin.murphy@....com>,
Joerg Roedel <joro@...tes.org>,
Baptiste Reynal <b.reynal@...tualopensystems.com>,
Alex Williamson <alex.williamson@...hat.com>,
Scott Branden <sbranden@...adcom.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>,
Linux IOMMU <iommu@...ts.linux-foundation.org>,
kvm@...r.kernel.org,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 5/5] vfio: platform: reset: Add Broadcom FlexRM reset module
On Wed, Jul 19, 2017 at 10:20 PM, Scott Branden
<scott.branden@...adcom.com> wrote:
> Hi Anup,
>
> NAK - as indicated in internal review please use unmodified Broadcom legal
> header in its own comment block.
I had addressed your internal review comments and used
standard GLPv2 header (also present in other drivers). The
only part I missed was to keep additional comments as
separate comment block (which you had not mentioned
in internal review).
Anyways, I will update the comment header but I think
using "NAK" in such situation is a bit over-kill
Regards,
Anup
Powered by blists - more mailing lists