From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Andy Gross <agross@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
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 hid tree with the qcom tree
Date: Mon, 15 Feb 2021 07:49:12 +1100 [thread overview]
Message-ID: <20210215074912.667768ff@canb.auug.org.au> (raw)
In-Reply-To: <20210119104536.50e08bac@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
Hi all,
On Tue, 19 Jan 2021 10:45:36 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the hid tree got a conflict in:
>
> arch/arm64/configs/defconfig
>
> between commit:
>
> 74b87103b3d0 ("arm64: defconfig: Enable HID multitouch")
>
> from the qcom tree and commit:
>
> 1fe16cfd311b ("arm64: defconfig: Update config names for i2c-hid rejigger")
>
> from the hid tree.
>
> I fixed it up (see below) 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.
>
> diff --cc arch/arm64/configs/defconfig
> index f2107444df08,326198305beb..000000000000
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@@ -756,14 -746,11 +756,15 @@@ CONFIG_SND_SOC_SIMPLE_AMPLIFIER=
> CONFIG_SND_SOC_TAS571X=m
> CONFIG_SND_SOC_WCD934X=m
> CONFIG_SND_SOC_WM8904=m
> +CONFIG_SND_SOC_WM8962=m
> CONFIG_SND_SOC_WSA881X=m
> +CONFIG_SND_SOC_LPASS_WSA_MACRO=m
> +CONFIG_SND_SOC_LPASS_VA_MACRO=m
> CONFIG_SND_SIMPLE_CARD=m
> CONFIG_SND_AUDIO_GRAPH_CARD=m
> +CONFIG_HID_MULTITOUCH=m
> - CONFIG_I2C_HID=m
> + CONFIG_I2C_HID_ACPI=m
> + CONFIG_I2C_HID_OF=m
> CONFIG_USB_CONN_GPIO=m
> CONFIG_USB=y
> CONFIG_USB_OTG=y
With the merge window about to open, this is a reminder that this
conflict still exists.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-14 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 23:45 Stephen Rothwell
2021-02-14 20:49 ` 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=20210215074912.667768ff@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agross@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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
all inboxes | Powered by JetHome®