Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20200402155057.30667-1-vaibhavgupta40@gmail.com>
 <CAHp75VcYSaAYx5qy7S0ppb77afgz=Ma=7=opfgSMCBnnjmoWfw@mail.gmail.com> <CAPBsFfAW6z=sP__SHj5Ln-3SHiYcLa4Me=CudAh3iw_Ypmr9mg@mail.gmail.com>
In-Reply-To: <CAPBsFfAW6z=sP__SHj5Ln-3SHiYcLa4Me=CudAh3iw_Ypmr9mg@mail.gmail.com>
From:   Vaibhav Gupta <vaibhav.varodek@gmail.com>
Date:   Fri, 3 Apr 2020 01:21:20 +0530
Message-ID: <CAPBsFfB9uUhZ24UV6heYuOf5_ss8Wx8bywGiq-1gq+h+S-JfWA@mail.gmail.com>
Subject: Fwd: [Linux-kernel-mentees] [PATCH v1] gpio: ml: ioh: Convert to dev_pm_ops
To:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

> Thank you for the patch.
>
> Rather then doing this I think  the best approach is to unify gpio-pch
> and gpio-ml-ioh together.
> Under umbrella of the task, the clean ups like above are highly appreciated.

Sure! So, will the patch be accepted or we should scrap it and work on
unifying the gpio-pch and gpio-ml-ioh and other similar driver(s) (if any)?

-- Vaibhav Gupta