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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Jan 2020 15:04:35 +0800
From:   me@...women.cn
To:     "Kohada.Tetsuhiro@...MitsubishiElectric.co.jp" 
        <Kohada.Tetsuhiro@...MitsubishiElectric.co.jp>
Cc:     'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>,
        "Mori.Takahiro@...MitsubishiElectric.co.jp" 
        <Mori.Takahiro@...MitsubishiElectric.co.jp>,
        "Motai.Hirotaka@...MitsubishiElectric.co.jp" 
        <Motai.Hirotaka@...MitsubishiElectric.co.jp>,
        'Valdis Kletnieks' <valdis.kletnieks@...edu>,
        "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
        "'devel@...verdev.osuosl.org'" <devel@...verdev.osuosl.org>,
        "'linux-fsdevel@...r.kernel.org'" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] staging: exfat: remove fs_func struct.

On Thu, Jan 23, 2020 at 06:38:53AM +0000, Kohada.Tetsuhiro@...MitsubishiElectric.co.jp wrote:
>Hello, Greg.
>
>Thank you for the quick reply.
>
>> Also the patch does not apply to the linux-next tree at all, so I can't take it.
>The patch I sent was based on the master branch of “https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/”
>and its tag was v5.5-rc6.
>
>> Also the patch does not apply to the linux-next tree at all, so I can't take it.  Please rebase and resend.
>I will send a new patch based on the latest master branch of “https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git”.
>
>
>By the way, could you answer below questions for my sending patches in future?
>1. Which repository and branch should be based when creating a new patch?
>2. How do I inform you about a base on which I create a patch?
If you like you can add [PATCH -next] to patch title before send it. :)
BR,
>
>--
>Best regards,
>Kohada Tetsuhiro <Kohada.Tetsuhiro@...MitsubishiElectric.co.jp>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ