linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Kumaravel Thiagarajan <kumaravel.thiagarajan@microchip.com>,
	linux-kernel@vger.kernel.org, sudipm.mukherjee@gmail.com,
	arnd@arndb.de, linux-gpio@vger.kernel.org,
	linux-next@vger.kernel.org, bagasdotme@gmail.com,
	zengheng4@huawei.com
Subject: Re: [PATCH v2 char-misc-next] misc: microchip: pci1xxxx: use DEFINE_SIMPLE_DEV_PM_OPS() in place  of the SIMPLE_DEV_PM_OPS() in pci1xxxx's gpio driver
Date: Thu, 22 Sep 2022 16:40:05 +0100	[thread overview]
Message-ID: <YyyB1at426/JLB3V@spud> (raw)
In-Reply-To: <Yyx3AMaETK2GsBHl@kroah.com>

On Thu, Sep 22, 2022 at 04:53:52PM +0200, Greg KH wrote:
> On Wed, Sep 21, 2022 at 05:48:45PM +0100, Conor Dooley wrote:
> > On Thu, Sep 15, 2022 at 03:17:29PM +0530, Kumaravel Thiagarajan wrote:
> > > misc: microchip: pci1xxxx: use DEFINE_SIMPLE_DEV_PM_OPS() in place  of the SIMPLE_DEV_PM_OPS() in pci1xxxx's gpio driver
> >                                                                     ^^
> > FYI, double space in the subject here, rather a mouthful though and
> > surely everything after SIMPLE_DEV_PM_OPS() is redundant?
> > 
> > > build errors listed below and reported by Sudip Mukherjee
> > > <sudipm.mukherjee@gmail.com> for the builds of
> > > riscv, s390, csky, alpha and loongarch allmodconfig are fixed in
> > > this patch.
> > 
> > allmodconfig has been broken for a while now, and this patch appears
> > to have been sitting for a week & a second fix has shown up at:
> > https://lore.kernel.org/all/20220919094250.858716-1-zengheng4@huawei.com/
> > 
> > I do note that Zeng Hang's patch does slightly more than this one does,
> > but idk about about the PM APIs /shrug.
> > 
> > Has this just slipped under the radar since so many of us were
> > attending conferences etc the last while or are you looking for
> > Kumaravel to do something more here?
> 
> I've taken this change now, sorry for the delay.  Was not looking at
> patches while at conferences.

Great, thanks Greg!

      reply	other threads:[~2022-09-22 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  9:47 [PATCH v2 char-misc-next] misc: microchip: pci1xxxx: use DEFINE_SIMPLE_DEV_PM_OPS() in place of the SIMPLE_DEV_PM_OPS() in pci1xxxx's gpio driver Kumaravel Thiagarajan
2022-09-21 16:48 ` Conor Dooley
2022-09-22  3:20   ` Zeng Heng
2022-09-22 14:53   ` Greg KH
2022-09-22 15:40     ` Conor Dooley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YyyB1at426/JLB3V@spud \
    --to=conor@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kumaravel.thiagarajan@microchip.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=zengheng4@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).