Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux5.2: Enable befs suppport
Date: Mon, 22 Jul 2019 18:32:06 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13284@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

There is a new pull request by Oreo639 against master on the void-packages repository

https://github.com/Oreo639/void-packages enable-befs
https://github.com/void-linux/void-packages/pull/13284

linux5.2: Enable befs suppport
This enables read only BeFS (officially called BFS) support for linux.
This is the filesystem used by Haiku OS.
If you want any changes, feel free to let me know ofc.

A patch file from https://github.com/void-linux/void-packages/pull/13284.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-enable-befs-13284.patch --]
[-- Type: application/text/x-diff, Size: 1358 bytes --]

From 379e9a42ade2dfa603d110ce9def10b01a9e7bf5 Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Mon, 22 Jul 2019 08:51:39 -0700
Subject: [PATCH] linux5.2: Enable befs suppport

---
 srcpkgs/linux5.2/files/i386-dotconfig   | 3 ++-
 srcpkgs/linux5.2/files/x86_64-dotconfig | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/linux5.2/files/i386-dotconfig b/srcpkgs/linux5.2/files/i386-dotconfig
index 601c1d1ba31..98dc1a1f70a 100644
--- a/srcpkgs/linux5.2/files/i386-dotconfig
+++ b/srcpkgs/linux5.2/files/i386-dotconfig
@@ -8397,7 +8397,8 @@ CONFIG_ECRYPT_FS=m
 # CONFIG_ECRYPT_FS_MESSAGING is not set
 CONFIG_HFS_FS=m
 CONFIG_HFSPLUS_FS=m
-# CONFIG_BEFS_FS is not set
+CONFIG_BEFS_FS=m
+# CONFIG_BEFS_DEBUG is not set
 # CONFIG_BFS_FS is not set
 # CONFIG_EFS_FS is not set
 # CONFIG_JFFS2_FS is not set
diff --git a/srcpkgs/linux5.2/files/x86_64-dotconfig b/srcpkgs/linux5.2/files/x86_64-dotconfig
index 0e05ed37e80..cee35c0ec99 100644
--- a/srcpkgs/linux5.2/files/x86_64-dotconfig
+++ b/srcpkgs/linux5.2/files/x86_64-dotconfig
@@ -8544,7 +8544,8 @@ CONFIG_ECRYPT_FS=m
 # CONFIG_ECRYPT_FS_MESSAGING is not set
 CONFIG_HFS_FS=m
 CONFIG_HFSPLUS_FS=m
-# CONFIG_BEFS_FS is not set
+CONFIG_BEFS_FS=m
+# CONFIG_BEFS_DEBUG is not set
 # CONFIG_BFS_FS is not set
 # CONFIG_EFS_FS is not set
 # CONFIG_JFFS2_FS is not set

             reply	other threads:[~2019-07-22 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 16:32 voidlinux-github [this message]
2019-07-22 16:33 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-22 16:33 ` voidlinux-github
2019-07-23  6:45 ` voidlinux-github
2019-07-23 14:55 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-23 14:55 ` voidlinux-github
2019-07-23 14:56 ` voidlinux-github
2019-07-23 14:57 ` voidlinux-github
2019-07-23 14:58 ` voidlinux-github
2019-07-23 15:00 ` voidlinux-github
2019-07-23 15:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-23 15:02 ` voidlinux-github
2019-07-23 19:11 ` [PR PATCH] [Merged]: " voidlinux-github

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13284@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).