public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Kaustabh Chakraborty <kauschluss@disroot•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Inki Dae <daeinki@gmail•com>, Inki Dae <inki.dae@samsung•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Dave Airlie <airlied@redhat•com>,
	DRI <dri-devel@lists•freedesktop.org>
Subject: Re: linux-next: build failure after merge of the drm-exynos tree
Date: Sun, 28 Sep 2025 15:31:58 +0000	[thread overview]
Message-ID: <309f74f9ee216e8a31a210fa22c414a6@disroot.org> (raw)
In-Reply-To: <20250912124721.535e89fc@canb.auug.org.au>

On 2025-09-12 02:47, Stephen Rothwell wrote:
> Hi all,
> 
> On Thu, 4 Sep 2025 07:59:23 +1000 Stephen Rothwell 
> <sfr@canb•auug.org.au> wrote:
>> 
>> On Wed, 03 Sep 2025 15:51:03 +0000 Kaustabh Chakraborty 
>> <kauschluss@disroot•org> wrote:
>> >
>> > This commit is from commit [1] of branch [2]. However, the macro is
>> > defined in commit [3] of branch [4]. I had sent those patches in a single
>> > patchset, though.
>> >
>> > I guess the merge strategy would be exynos-drm-misc-next, followed by exynos-drm-next.
>> >
>> > Let me know if you need to know anything else. Thanks!
>> >
>> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/commit/?h=exynos-drm-next&id=d07e4c00696f53510ec8a23dcba0c4ac87840874
>> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/log/?h=exynos-drm-next
>> >
>> > [3] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/commit/?h=exynos-drm-misc-next&id=bcd0d93e902e54e6b404b574b3a6b23315bcea8d
>> > [4] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/log/?h=exynos-drm-misc-next
>> 
>> The problem is that nobody has ever asked me to merge [4] into
>> linux-next ... I also presume that it will be merged into the 
>> drm-fixes
>> tree (or Linus' tree) at some point and that hasn't happened either.
> 
> This is still failing ... and it has been since Aug 21!

Hi, can you can try merging it again? The macro is in linux-next now.

> 
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2025-09-28 15:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  1:27 linux-next: build failure after merge of the drm-exynos tree Stephen Rothwell
2025-08-26  2:13 ` Stephen Rothwell
2025-09-01  2:22   ` Stephen Rothwell
2025-09-02  3:03     ` Stephen Rothwell
2025-09-03 15:51       ` Kaustabh Chakraborty
2025-09-03 21:59         ` Stephen Rothwell
2025-09-12  2:47           ` Stephen Rothwell
2025-09-28 15:31             ` Kaustabh Chakraborty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-17  3:51 Stephen Rothwell
2015-08-17  3:53 ` Stephen Rothwell
2015-08-17  5:53   ` Stephen Rothwell
2015-08-17  7:08     ` Inki Dae
2015-08-18  3:02       ` Stephen Rothwell
2015-06-23  1:52 Stephen Rothwell
2015-06-23  5:30 ` Inki Dae
2015-06-24  1:01 ` Stephen Rothwell
2015-06-24  1:21   ` Inki Dae
2015-06-24  1:25     ` Dave Airlie
2015-06-24  1:25     ` Inki Dae

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=309f74f9ee216e8a31a210fa22c414a6@disroot.org \
    --to=kauschluss@disroot$(echo .)org \
    --cc=airlied@redhat$(echo .)com \
    --cc=daeinki@gmail$(echo .)com \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=inki.dae@samsung$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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