All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild@lists.01.org
Subject: Re: [brauner:debugfs_namespaces 3/5] kernel/utsname.c:108 copy_utsname() error: 'new_ns' dereferencing possible ERR_PTR()
Date: Mon, 07 Oct 2019 13:26:18 +0300	[thread overview]
Message-ID: <20191007102618.GF21515@kadam> (raw)
In-Reply-To: <20191007100530.xnpvxrhbl77yabjr@wittgenstein>

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

On Mon, Oct 07, 2019 at 12:05:31PM +0200, Christian Brauner wrote:
> On Mon, Oct 07, 2019 at 12:57:57PM +0300, Dan Carpenter wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git debugfs_namespaces
> > head:   aef8406e30cf9b60c76e5de205fa77f3791e2c54
> > commit: fce9acb4ffd1b7b342c69f0c39d49835b7232414 [3/5] DEBUG
> > 
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> I'm very confused about this mail. This is a pure development branch
> that is not tracked by anything and is in extremely rough shape... So
> why exactly is this happening? :) I'm really asking, not complaining.

kbuild tries to be as helpful as possible.  :)  There is a way to turn
it off for devel trees.  It's probably described in the FAQ but who
cares, just leave it on.  It doesn't cost me anything to send these
emails.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild-all@lists.01.org
Subject: Re: [brauner:debugfs_namespaces 3/5] kernel/utsname.c:108 copy_utsname() error: 'new_ns' dereferencing possible ERR_PTR()
Date: Mon, 07 Oct 2019 13:26:18 +0300	[thread overview]
Message-ID: <20191007102618.GF21515@kadam> (raw)
In-Reply-To: <20191007100530.xnpvxrhbl77yabjr@wittgenstein>

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

On Mon, Oct 07, 2019 at 12:05:31PM +0200, Christian Brauner wrote:
> On Mon, Oct 07, 2019 at 12:57:57PM +0300, Dan Carpenter wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git debugfs_namespaces
> > head:   aef8406e30cf9b60c76e5de205fa77f3791e2c54
> > commit: fce9acb4ffd1b7b342c69f0c39d49835b7232414 [3/5] DEBUG
> > 
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> I'm very confused about this mail. This is a pure development branch
> that is not tracked by anything and is in extremely rough shape... So
> why exactly is this happening? :) I'm really asking, not complaining.

kbuild tries to be as helpful as possible.  :)  There is a way to turn
it off for devel trees.  It's probably described in the FAQ but who
cares, just leave it on.  It doesn't cost me anything to send these
emails.

regards,
dan carpenter

       reply	other threads:[~2019-10-07 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191007100530.xnpvxrhbl77yabjr@wittgenstein>
2019-10-07 10:26 ` Dan Carpenter [this message]
2019-10-07 10:26   ` [brauner:debugfs_namespaces 3/5] kernel/utsname.c:108 copy_utsname() error: 'new_ns' dereferencing possible ERR_PTR() Dan Carpenter
2019-10-07  9:57 Dan Carpenter
2019-10-07  9:57 ` Dan Carpenter

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=20191007102618.GF21515@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=kbuild@lists.01.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 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.