Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1585946
| From | Daniel Borkmann <daniel@iogearbox.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: manual merge of the kspp tree with the net-next tree |
| Date | 2017-02-22 07:40 +0100 |
| Message-ID | <tdyKJ-5Ut-1@gated-at.bofh.it> (permalink) |
| References | <tdsvD-1fc-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 02/22/2017 12:51 AM, Stephen Rothwell wrote:
> Hi Kees,
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> arch/arm/Kconfig
>
> between commit:
>
> d2852a224050 ("arch: add ARCH_HAS_SET_MEMORY config")
>
> from the net-next tree and commit:
>
> ad21fc4faa2a ("arch: Move CONFIG_DEBUG_RODATA and CONFIG_SET_MODULE_RONX to be common")
>
> from the kspp 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.
Also looks good to me.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
linux-next: manual merge of the kspp tree with the net-next tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-02-22 01:00 +0100 Re: linux-next: manual merge of the kspp tree with the net-next tree Daniel Borkmann <daniel@iogearbox.net> - 2017-02-22 07:40 +0100
csiph-web