From: Dan Williams <dan.j.williams@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Dan Williams <dan.j.williams@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: manual merge of the cxl-fixes tree with Linus' tree
Date: Mon, 26 Feb 2024 15:01:49 -0800 [thread overview]
Message-ID: <65dd185d2eba8_2bca029498@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
In-Reply-To: <20240226090417.65ba3c4b@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the cxl-fixes tree got a conflict in:
>
> drivers/cxl/acpi.c
>
> between commit:
>
> 5c6224bfabbf ("cxl/acpi: Fix load failures due to single window creation failure")
>
> from Linus' tree and commit:
>
> 5141fa1ec23f ("cxl/acpi: Fix load failures due to single window creation failure")
>
> from the cxl-fixes tree.
>
> I fixed it up (I just used the version from Linus' tree) and can carry the
> fix as necessary. This is now fixed as far as linux-next is concerned,
> but any non trivial conflicts should be mentioned to your upstream
> maintainer when your tree is submitted for merging. You may also want
> to consider cooperating with the maintainer of the conflicting tree to
> minimise any particularly complex conflicts.
Thanks, Steven. Will drop that out of the fixes branch. I ended up with
a late refresh of what was included in the tagged pull vs what was
soaking in linux-next.
next prev parent reply other threads:[~2024-02-26 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 22:04 linux-next: manual merge of the cxl-fixes tree with Linus' tree Stephen Rothwell
2024-02-26 23:01 ` Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-18 22:07 Stephen Rothwell
2024-02-18 23:00 ` Dan Williams
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=65dd185d2eba8_2bca029498@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@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