From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c7def606493b4765265c44730b5d57da901e49ef
Date: Mon, 03 Jun 2019 09:20:18 +0100 [thread overview]
Message-ID: <20190603082019.1389984FDC8@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via c7def606493b4765265c44730b5d57da901e49ef (commit)
from 99597de716394f665fa745d4ef3784c5b495d02e (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c7def606493b4765265c44730b5d57da901e49ef
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 3 09:20:05 2019 +0100
Rootfile update
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/aarch64/linux | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/config/rootfiles/common/aarch64/linux b/config/rootfiles/common/aarch64/linux
index 4892eb6c5..3c5f6d08d 100644
--- a/config/rootfiles/common/aarch64/linux
+++ b/config/rootfiles/common/aarch64/linux
@@ -11655,6 +11655,7 @@ etc/modprobe.d/ipv6.conf
#lib/modules/KVER-ipfire/build/include/linux/bitmap.h
#lib/modules/KVER-ipfire/build/include/linux/bitops.h
#lib/modules/KVER-ipfire/build/include/linux/bitrev.h
+#lib/modules/KVER-ipfire/build/include/linux/bits.h
#lib/modules/KVER-ipfire/build/include/linux/blk-cgroup.h
#lib/modules/KVER-ipfire/build/include/linux/blk-mq-pci.h
#lib/modules/KVER-ipfire/build/include/linux/blk-mq-rdma.h
@@ -14154,6 +14155,7 @@ etc/modprobe.d/ipv6.conf
#lib/modules/KVER-ipfire/build/include/net/ipcomp.h
#lib/modules/KVER-ipfire/build/include/net/ipconfig.h
#lib/modules/KVER-ipfire/build/include/net/ipv6.h
+#lib/modules/KVER-ipfire/build/include/net/ipv6_frag.h
#lib/modules/KVER-ipfire/build/include/net/ipx.h
#lib/modules/KVER-ipfire/build/include/net/iucv
#lib/modules/KVER-ipfire/build/include/net/iucv/af_iucv.h
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-03 8:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190603082019.1389984FDC8@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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