From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-intel tree
Date: Fri, 16 May 2025 19:56:29 +1000 [thread overview]
Message-ID: <20250516195629.1d15d4ad@canb.auug.org.au> (raw)
In-Reply-To: <aCcLH25PSNqtPeSk@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
Hi Andy,
On Fri, 16 May 2025 12:53:35 +0300 Andy Shevchenko <andriy.shevchenko@linux•intel.com> wrote:
>
> I have just sent 20250516095306.3417798-1-andriy.shevchenko@linux•intel.com, it
> should fix the error here.
Thanks. Hopefully that will be in the gpio-intel tree soon.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-05-16 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 9:34 linux-next: build failure after merge of the gpio-intel tree Stephen Rothwell
2025-05-16 9:36 ` Andy Shevchenko
2025-05-16 9:42 ` Stephen Rothwell
2025-05-16 9:53 ` Andy Shevchenko
2025-05-16 9:56 ` Stephen Rothwell [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=20250516195629.1d15d4ad@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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