All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
	mm-commits@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v5.1] printk: Add kernel parameter to control writes to /dev/kmsg
Date: Mon, 25 Jul 2016 08:38:06 +0200	[thread overview]
Message-ID: <20160725063806.GA24597@nazgul.tnic> (raw)
In-Reply-To: <201607250034.72IAmpIe%fengguang.wu@intel.com>

On Mon, Jul 25, 2016 at 12:55:55AM +0800, kbuild test robot wrote:
> Hi,
> 
> [auto build test ERROR on stable/master]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> 
> url:    https://github.com/0day-ci/linux/commits/Borislav-Petkov/printk-Add-kernel-parameter-to-control-writes-to-dev-kmsg/20160725-003035
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git master

Yes, that's definitely the wrong tree.

Those patches are queued in the mm tree, you can test that one.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--

      reply	other threads:[~2016-07-25  6:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 21:27 + printk-add-kernel-parameter-to-control-writes-to-dev-kmsg-checkpatch-fixes.patch added to -mm tree akpm
2016-07-19  7:23 ` Borislav Petkov
2016-07-24 16:55   ` [PATCH -v5.1] printk: Add kernel parameter to control writes to /dev/kmsg kbuild test robot
2016-07-25  6:38     ` Borislav Petkov [this message]

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=20160725063806.GA24597@nazgul.tnic \
    --to=bp@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mm-commits@vger.kernel.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.