All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bastien Curutchet <bastien.curutchet@bootlin.com>
Cc: kernel test robot <lkp@intel.com>, oe-kbuild-all@lists.linux.dev
Subject: Re: [char-misc:char-misc-testing 34/74] drivers/pps/clients/pps-gpio.c:66:47: error: incompatible type for argument 1 of '_dev_warn'
Date: Wed, 8 Jan 2025 14:18:44 +0100	[thread overview]
Message-ID: <2025010834-recycled-blinked-37c4@gregkh> (raw)
In-Reply-To: <da411c8f-719b-4bd6-8314-4200b115a405@bootlin.com>

On Wed, Jan 08, 2025 at 01:44:25PM +0100, Bastien Curutchet wrote:
> Hi Greg,
> 
> On 1/8/25 1:19 PM, Greg Kroah-Hartman wrote:
> > On Wed, Jan 08, 2025 at 03:37:10AM +0800, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-testing
> > > head:   daec45916d68bc14406f20f547a8c39a3eab88b3
> > > commit: 8aa0545f419e5bffbb27354e0221997cb6e87cbd [34/74] pps: clients: gpio: Bypass edge's direction check when not needed
> > 
> > Bastien, I've now dropped this commit from my branches, please fix it up
> > and resend (after at least test-building it...)
> > 
> 
> I've investigated it, it's a conflict with commit c79a39dc8d060 ("pps: Fix a
> use-after-free") that changes the struct pps_device. This commit isn't
> present in v6.13-rc3.
> 
> Do you want me to send a new patch based on char-misc-testing ?

Please do.

thanks,

greg k-h

      reply	other threads:[~2025-01-08 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 19:37 [char-misc:char-misc-testing 34/74] drivers/pps/clients/pps-gpio.c:66:47: error: incompatible type for argument 1 of '_dev_warn' kernel test robot
2025-01-08 12:19 ` Greg Kroah-Hartman
2025-01-08 12:44   ` Bastien Curutchet
2025-01-08 13:18     ` Greg Kroah-Hartman [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=2025010834-recycled-blinked-37c4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bastien.curutchet@bootlin.com \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.