From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 auxdisplay tree
Date: Thu, 3 Oct 2024 13:07:44 +0300 [thread overview]
Message-ID: <Zv5s8BbsBKV9lE4L@smile.fi.intel.com> (raw)
In-Reply-To: <20241003124608.7eb3f1fb@canb.auug.org.au>
On Thu, Oct 03, 2024 at 12:46:08PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the auxdisplay tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/auxdisplay/ht16k33.c: No such file or directory
>
> Caused by commit
>
> 7f11dc1a9ca9 ("auxdisplay: ht16k33: Make use of i2c_get_match_data()")
>
> I have used the auxdisplay tree from next-20241002 for today.
Thank you for catching this! It seems the malformed change was pushed into
repository. For an unknown reason I have got the driver renamed. Fixed now.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-10-03 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 2:46 linux-next: build failure after merge of the auxdisplay tree Stephen Rothwell
2024-10-03 10:07 ` Andy Shevchenko [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=Zv5s8BbsBKV9lE4L@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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