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>] [day] [month] [year] [list]
Message-ID: <mhng-6ceee60c-0277-4a89-9bf8-9fd875250ac4@palmer-si-x1c4>
Date:   Wed, 13 Sep 2017 13:18:17 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...belt.com>
To:     Arnd Bergmann <arnd@...db.de>
CC:     peterz@...radead.org, tglx@...utronix.de, jason@...edaemon.net,
        marc.zyngier@....com, dmitriy@...-tech.org,
        yamada.masahiro@...ionext.com, mmarek@...e.com, albert@...ive.com,
        will.deacon@....com, boqun.feng@...il.com, oleg@...hat.com,
        mingo@...hat.com, daniel.lezcano@...aro.org,
        gregkh@...uxfoundation.org, jslaby@...e.com, davem@...emloft.net,
        mchehab@...nel.org, hverkuil@...all.nl, rdunlap@...radead.org,
        viro@...iv.linux.org.uk, mhiramat@...nel.org, fweisbec@...il.com,
        mcgrof@...nel.org, dledford@...hat.com, bart.vanassche@...disk.com,
        sstabellini@...nel.org, mpe@...erman.id.au,
        rmk+kernel@...linux.org.uk, paul.gortmaker@...driver.com,
        nicolas.dichtel@...nd.com, linux@...ck-us.net,
        heiko.carstens@...ibm.com, schwidefsky@...ibm.com,
        geert@...ux-m68k.org, akpm@...ux-foundation.org,
        andriy.shevchenko@...ux.intel.com, jiri@...lanox.com,
        vgupta@...opsys.com, airlied@...hat.com, jk@...abs.org,
        chris@...is-wilson.co.uk, Jason@...c4.com,
        paulmck@...ux.vnet.ibm.com, ncardwell@...gle.com,
        linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
        patches@...ups.riscv.org
Subject:     Re: RISC-V Linux Port v8

On Wed, 13 Sep 2017 09:15:39 PDT (-0700), Arnd Bergmann wrote:
> On Tue, Sep 12, 2017 at 11:56 PM, Palmer Dabbelt <palmer@...belt.com> wrote:
>> I know it may not be the ideal time to submit a patch set right now, as it's
>> the middle of the merge window, but things have calmed down quite a bit in the
>> last month so I thought it would be good to get everyone on the same page.
>> There's been a handful of changes since the last patch set, but most of them
>> are fairly minor:
>>
>> * We changed PAGE_OFFSET to allowing mapping more physical memory on 64-bit
>>   systems.  This is user configurable, as it triggers a different code model
>>   that generates slightly less efficient code.
>> * The device tree binding documentation is back, I'd managed to lose it at some
>>   point.
>> * We now pass the atomic64 test suite.
>> * The SBI timer driver has been refactored.
>>
>> To the best of by knowledge, all the feedback we've gotten so far has been
>> taken into account for this patch set.  If I've missed anyone's feedback I'm
>> sorry, just point it out and I'll try to dig it up.
>>
>> Just to be clear on timelines: we're not pushing to get into 4.14, but we are
>> hoping we can make it in for 4.15.  If I understand the process correctly, we
>> should aim to get into linux-next some time in the next month so we can be
>> merged during the next merge window.
>
> I looked at all patches again and found a few minor things that we
> should clarify, but overall I think this looks good.

Thanks!

> What I think you should do as the next step is to separate the
> architecture specific changes from the device drivers and put
> them into one branch that you ask Stephen Rothwell to add to
> linux-next.

OK.  Would it be possible to get the MAINTAINERS patch merged as part of this
merge window?  If I'm ready to actually start getting things merged I'd like to
have a proper tree and I've been told this is a prerequisite.

> For the driver patches, I would submit them separately now
> with a reduced Cc-list that just contains the respective
> subsystem maintainers as well as the relevant mailing lists.

Makes sense.  I'll wait a bit for some more feedback and if there's nothing
major then I'll split things up for the v9.

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ