public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd•com>
Cc: Richard Weinberger <richard.weinberger@gmail•com>,
	Miquel Raynal <miquel.raynal@bootlin•com>,
	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 mtd tree
Date: Tue, 2 Sep 2025 15:45:05 +1000	[thread overview]
Message-ID: <20250902154505.3bcd048a@canb.auug.org.au> (raw)
In-Reply-To: <IA0PR12MB76998C672B82567715227485DC06A@IA0PR12MB7699.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 393 bytes --]

Hi Amit,

On Tue, 2 Sep 2025 05:25:04 +0000 "Mahapatra, Amit Kumar" <amit.kumar-mahapatra@amd•com> wrote:
>
> Could you please share the tree you are using along with the build
> steps you followed that resulted in this issue?

https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git
branch mtd/next

I just did an x86_64 allmodconfig build.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-09-02  5:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  2:08 linux-next: build failure after merge of the mtd tree Stephen Rothwell
2025-09-02  5:25 ` Mahapatra, Amit Kumar
2025-09-02  5:45   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-12 13:14 Mark Brown
2026-03-12 14:22 ` Andy Shevchenko
2026-01-30 15:47 Mark Brown
2026-02-02  8:47 ` Miquel Raynal
2021-02-15  1:28 Stephen Rothwell
2021-02-15  8:55 ` Rafał Miłecki
2010-04-08  1:42 Stephen Rothwell

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=20250902154505.3bcd048a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=amit.kumar-mahapatra@amd$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=miquel.raynal@bootlin$(echo .)com \
    --cc=richard.weinberger@gmail$(echo .)com \
    /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