From: Luca Coelho <luca@coelho.fi>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Kalle Valo <kvalo@codeaurora.org>,
Wireless <linux-wireless@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: manual merge of the net-next tree with the wireless-drivers tree
Date: Mon, 29 Apr 2019 08:19:34 +0300 [thread overview]
Message-ID: <cc5e71b2ae7c72b643b9666897bbf6eda4bddbb6.camel@coelho.fi> (raw)
In-Reply-To: <20190429115338.5decb50b@canb.auug.org.au>
Hi Stephen,
On Mon, 2019-04-29 at 11:54 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> drivers/net/wireless/intel/iwlwifi/mvm/debugfs-vif.c
>
> between commits:
>
> 154d4899e411 ("iwlwifi: mvm: properly check debugfs dentry before using it")
> d156e67d3f58 ("iwlwifi: mvm: fix merge damage in iwl_mvm_vif_dbgfs_register()")
>
> from the wireless-drivers tree and commit:
>
> c9af7528c331 ("iwlwifi: mvm: no need to check return value of debugfs_create functions")
>
> from the net-next tree.
>
> I fixed it up (the latter removed the code modified by the former, so I
> just did that) 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.
I checked your merge and it looks good, thanks!
--
Cheers,
Luca.
next prev parent reply other threads:[~2019-04-29 5:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 1:54 Stephen Rothwell
2019-04-29 5:19 ` Luca Coelho [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-09 0:39 Stephen Rothwell
2016-05-10 6:43 ` Kalle Valo
2016-02-29 1:56 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=cc5e71b2ae7c72b643b9666897bbf6eda4bddbb6.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®