[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7561edb-be14-d78e-0f97-54ef6bd4eaea@ti.com>
Date: Wed, 8 Mar 2023 10:20:13 -0600
From: Andrew Davis <afd@...com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
CC: Bartosz Golaszewski <brgl@...ev.pl>,
Peter Tyser <ptyser@...-inc.com>,
Andy Shevchenko <andy@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
<linux-gpio@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/6] gpio: sch311x: Use devm_gpiochip_add_data() to
simplify remove path
On 3/8/23 9:53 AM, Andy Shevchenko wrote:
> On Wed, Mar 8, 2023 at 5:50 PM Andrew Davis <afd@...com> wrote:
>> On 3/8/23 4:32 AM, Bartosz Golaszewski wrote:
>>> On Wed, Mar 8, 2023 at 11:24 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> ...
>
>>> I see there's v2 out, backing it out then.
>>
>> Looks like I missed something that kernel test robot found, so there
>> will be a v3.
>
> Just split your series on a per driver basis. This will help with
> understanding what's going on. Also use a cover letter to explain what
> your series is for.
>
There is one patch per driver, not sure what you mean by split per driver?
Will add a cover letter for v3 and drop the first patch that's in your tree already.
Andrew
Powered by blists - more mailing lists