linux-kernel - Re: [PATCH v2] fs: inode: return proper error code in bmap()

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: <ff0d7038-8a53-f183-fc3a-d69143e801a2@wewakecorp.com>
Date:   Sat, 15 Jul 2023 22:20:43 +0900
From:   Leesoo Ahn <lsahn@...akecorp.com>
To:     Markus Elfring <Markus.Elfring@....de>,
        Leesoo Ahn <lsahn@...eel.net>, linux-fsdevel@...r.kernel.org,
        kernel-janitors@...r.kernel.org,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Christian Brauner <brauner@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] fs: inode: return proper error code in bmap()

2023-07-15 오후 9:50에 Markus Elfring 이(가) 쓴 글:
> 
> * How do you think about to add the tag “Fixes”?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc1#n591I think the description is enough, but still open to listen for that 
from others.

> 
> * Would you like to avoid a checkpatch warning by the specification
> of the tag “From” before your improved change description?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.5-rc1#n499
I use both emails and don't think that's a big deal. But if that 
matters, I will post v3 for that or maintainers could sync up the email 
of author by hands when they merge it.

thank you for your opinion,
Leesoo