From andre@ignavus.net Thu Nov 30 04:29:12 2017 Received: from mail-io0-f173.google.com ([209.85.223.173]) by stoneboat.default.lvansomeren.uk0.bigv.io with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1eKGTC-0005JD-Fl for yaffs@stoneboat.aleph1.co.uk; Thu, 30 Nov 2017 04:29:11 +0000 Received: by mail-io0-f173.google.com with SMTP id t196so6164901iof.0 for ; Wed, 29 Nov 2017 20:29:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ignavus-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=JIXDiEseFyQDK9UGyVl1Rw6XHWmdHPhicdyG29m3fmk=; b=CQ0+cBzpXaY8viqKCVtmoyqxfmr6FVIgJE94OQ0bBJGuWomW6WJGQM4h1thzjuZqFY u1srlZSyTeFLJ4X3RCKiQtdFHasOHu9e8QWkxxClogVyouDBCe9xKbQqk78+dkQYBL0P BbhxzJ9ta0LwB4a2JIRLEucB924t9yLaDbk3AHreMN5rSbFptEwPUQP7pdUKFFu0xi5W M25M+n0z851Y/v59vnxTJ39JOVqoNkbcqJe2JQnuqn98mZ9lLsxdzCiH6wnQ8XpdLPh3 6JalD8HQUY5MVlSjHTaC8Xb77QhWTB5jtyi7sjHExz6ackvaJ34+iltWGEqMefnrWxx8 dOQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=JIXDiEseFyQDK9UGyVl1Rw6XHWmdHPhicdyG29m3fmk=; b=RqHIbus5g4pIwqIv0FL/SXEAg3lZB9Yi+PQZ2qIxcp2ubNnzT0JNj+EdArz84aGFAb J1zSdbpSBejrGNokz3+zXRHWOfE5kprJc8uHc3r/zrZLtBfiKQ+8M5RE0IOyje/jnrpF DsuA9kNzAETgPX4GMgMljkFRvgZWqx/RNzV5VEdz3ozbPl1Ehp9XV8BHMnNtMMRmes3j emJgHivWo33xwbpIv4b8fpgHmFJeqPGjpXMBa18d1ZmZQGWxGHGiUlla1c9d/aoNzZ13 GJ/0RVLKAbY7JmYdktz6kFQp/A9rHs4SKsiju7xpnwDA9kH3Ahcl5e1PlZJa0JjVY1/u ZKnw== X-Gm-Message-State: AJaThX4EEBzD1x7Pr+p0EnRcZShRGmojqC6uVvaQieC0c60/WgwSoLrL JLRk1KeJF8DWld4uLPXAZBgQ/2AeZ9Z2NFAbyEXkKE9D X-Google-Smtp-Source: AGs4zMZQu+9NhhVk8SPISX3BgCXuxnI5hay+rXeYifpS8Ctzl/ddGTFQskPFZJZWuhn1Lkh7PGvtDVf7aB2uahHj+fA= X-Received: by 10.107.201.206 with SMTP id z197mr6255847iof.98.1512016144434; Wed, 29 Nov 2017 20:29:04 -0800 (PST) MIME-Version: 1.0 From: Andre Renaud Date: Thu, 30 Nov 2017 04:28:54 +0000 Message-ID: To: "yaffs@stoneboat.aleph1.co.uk" Content-Type: multipart/alternative; boundary="94eb2c0b9eec2f2428055f2bb100" X-Spam_score: -2.1 X-Spam_score_int: -20 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "stoneboat.default.lvansomeren.uk0.bigv.io", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I sent through a patch a while ago that fixed building YAFFS on new kernels (https://yaffs.net/lurker/message/20170507.214229.ce03d9f1.pt-BR.html). But the way it did that was basically by disabling xattr support. I've got a new patch which reinstates it again, but it's a bit more invasive since we now end up with three different prototypes for the yaffs_getxattr & yaffs_setxattr functions. Any comments on this? https://github.com/AndreRenaud/yaffs/commit/119ea499deecbf33035748b089730bb093cda605 [...] Content analysis details: (-2.1 points, 4.9 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.1 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2) [209.85.223.173 listed in wl.mailspike.net] -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.223.173 listed in list.dnswl.org] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: yaffs.net] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 AWL AWL: Adjusted score from AWL reputation of From: address X-SA-Exim-Connect-IP: 209.85.223.173 X-SA-Exim-Mail-From: andre@ignavus.net X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on stoneboat.default.lvansomeren.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.1 required=4.9 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.1 X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.default.lvansomeren.uk0.bigv.io) Subject: [Yaffs] XAttr support in new kernels X-BeenThere: yaffs@stoneboat.aleph1.co.uk X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 04:29:12 -0000 --94eb2c0b9eec2f2428055f2bb100 Content-Type: text/plain; charset="UTF-8" I sent through a patch a while ago that fixed building YAFFS on new kernels (https://yaffs.net/lurker/message/20170507.214229.ce03d9f1.pt-BR.html). But the way it did that was basically by disabling xattr support. I've got a new patch which reinstates it again, but it's a bit more invasive since we now end up with three different prototypes for the yaffs_getxattr & yaffs_setxattr functions. Any comments on this? https://github.com/AndreRenaud/yaffs/commit/119ea499deecbf33035748b089730bb093cda605 Regards, Andre --94eb2c0b9eec2f2428055f2bb100 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I sent through a patch a while ago that fixed building YAF= FS on new kernels (https://yaffs.net/lurker/message/20170507.214229.c= e03d9f1.pt-BR.html). But the way it did that was basically by disabling= xattr support. I've got a new patch which reinstates it again, but it&= #39;s a bit more invasive since we now end up with three different prototyp= es for the yaffs_getxattr & yaffs_setxattr functions.
Any comments = on this?

Regards,
Andre
--94eb2c0b9eec2f2428055f2bb100--