linux-kernel - Re: linux-next: manual merge of the parisc-hd tree with the asm-generic tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 22 Mar 2022 21:01:29 +0100
From:   Helge Deller <deller@....de>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Parisc List <linux-parisc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the parisc-hd tree with the
 asm-generic tree

On 3/22/22 18:06, Arnd Bergmann wrote:
> On Tue, Mar 22, 2022 at 8:34 AM Helge Deller <deller@....de> wrote:
>>
>> On 3/22/22 01:09, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> On Mon, 28 Feb 2022 11:45:23 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>>
>>>> Today's linux-next merge of the parisc-hd tree got a conflict in:
>>>>
>>>>   arch/parisc/lib/memcpy.c
>>>>
>>>> between commit:
>>>>
>>>>   967747bbc084 ("uaccess: remove CONFIG_SET_FS")
>>>>
>>>> from the asm-generic tree and commit:
>>>>
>>>>   d4a767ea8b0e ("parisc: Use constants to encode the space registers like SR_KERNEL")
>>>>
>>>> from the parisc-hd tree.
>>>
>>> This is now a conflict between the asm-generic tree and commit
>>>
>>>   360bd6c65807 ("parisc: Use constants to encode the space registers like SR_KERNEL")
>>>
>>> in Linus' tree.
>>
>>
>> Arnd,
>> can you please drop the changes in your asm-generic tree for
>> arch/parisc/lib/memcpy.c
>> They are not needed any more.
>>
>
> Sorry I missed that earlier when the conflict happened originally.
>
> I can't really rebase my changes on top of your tree now, and just dropping
> the change without a rebase would break mine. I'll make sure to mention
> the conflict in the pull request then and have Linus resolve it.

Ok, Thanks!

Helge