From: Mike Galbraith <efault@gmx.de>
To: Randy Dunlap <rdunlap@infradead.org>,
Damian Tometzki <damian.tometzki@icloud.com>,
Pintu Kumar <pintu.ping@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Re: How to verify linux-next
Date: Sun, 01 Oct 2017 19:03:03 +0200 [thread overview]
Message-ID: <1506877383.5529.1.camel@gmx.de> (raw)
In-Reply-To: <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org>
On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote:
> On 10/01/17 09:44, Damian Tometzki wrote:
>
> > i resolved the issue with:
> > sudo /etc/init.d/apparmor stop
>
> or boot with: apparmor=0
or systemctl mask apparmor
WARNING: multiple messages have this Message-ID (diff)
From: efault@gmx.de (Mike Galbraith)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to verify linux-next
Date: Sun, 01 Oct 2017 19:03:03 +0200 [thread overview]
Message-ID: <1506877383.5529.1.camel@gmx.de> (raw)
In-Reply-To: <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org>
On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote:
> On 10/01/17 09:44, Damian Tometzki wrote:
>
> > i resolved the issue with:
> > sudo /etc/init.d/apparmor stop
>
> or boot with: apparmor=0
or systemctl mask apparmor
next prev parent reply other threads:[~2017-10-01 17:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 9:42 How to verify linux-next Pintu Kumar
2017-09-29 9:46 ` Pintu Kumar
2017-09-29 9:46 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 12:41 ` valdis.kletnieks
2017-09-29 12:41 ` valdis.kletnieks at vt.edu
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 15:45 ` valdis.kletnieks
2017-09-29 15:45 ` valdis.kletnieks at vt.edu
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 11:04 ` valdis.kletnieks
2017-10-02 11:04 ` valdis.kletnieks at vt.edu
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 21:50 ` Theodore Ts'o
2017-09-29 21:50 ` Theodore Ts'o
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 5:25 ` Theodore Ts'o
2017-09-30 5:25 ` Theodore Ts'o
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 17:03 ` Mike Galbraith [this message]
2017-10-01 17:03 ` Mike Galbraith
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 16:47 ` Theodore Ts'o
2017-10-01 16:47 ` Theodore Ts'o
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=1506877383.5529.1.camel@gmx.de \
--to=efault@gmx.de \
--cc=damian.tometzki@icloud.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
--cc=rdunlap@infradead.org \
--cc=tytso@mit.edu \
--cc=valdis.kletnieks@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.