All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: [0-Day CI notification] kbuild test robot will be combined with kernel test robot
Date: Wed, 03 Jun 2020 15:24:13 +0800	[thread overview]
Message-ID: <20200603072413.GA29050@intel.com> (raw)

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

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for
subscribing to the service. It has been a long time we use both kbuild test
robot and kernel test robot to send out report. From now on, we want to
combine two mails to kernel test robot, which is a single voice for the
whole service. Sorry for any inconvenience caused by this change, which may
impact your mail setting.

Meanwhile, we have mail address lkp(a)intel.com for you to reach us. Kindly
drop us mail at kernel test robot <lkp@intel.com> or submit issue at
https://github.com/intel/lkp-tests for any question and support you need.

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: [0-Day CI notification] kbuild test robot will be combined with kernel test robot
Date: Wed, 03 Jun 2020 15:24:13 +0800	[thread overview]
Message-ID: <20200603072413.GA29050@intel.com> (raw)

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

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for
subscribing to the service. It has been a long time we use both kbuild test
robot and kernel test robot to send out report. From now on, we want to
combine two mails to kernel test robot, which is a single voice for the
whole service. Sorry for any inconvenience caused by this change, which may
impact your mail setting.

Meanwhile, we have mail address lkp(a)intel.com for you to reach us. Kindly
drop us mail at kernel test robot <lkp@intel.com> or submit issue at
https://github.com/intel/lkp-tests for any question and support you need.

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Philip Li <philip.li@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
	kbuild-all@lists.01.org, lkp@lists.01.org,
	kernel test robot <lkp@intel.com>
Subject: [0-Day CI notification] kbuild test robot will be combined with kernel test robot
Date: Wed, 3 Jun 2020 15:24:13 +0800	[thread overview]
Message-ID: <20200603072413.GA29050@intel.com> (raw)

Hi all, this is Philip who maintains the 0-Day CI test service. Thanks for
subscribing to the service. It has been a long time we use both kbuild test
robot and kernel test robot to send out report. From now on, we want to
combine two mails to kernel test robot, which is a single voice for the
whole service. Sorry for any inconvenience caused by this change, which may
impact your mail setting.

Meanwhile, we have mail address lkp@intel.com for you to reach us. Kindly
drop us mail at kernel test robot <lkp@intel.com> or submit issue at
https://github.com/intel/lkp-tests for any question and support you need.

Thanks

             reply	other threads:[~2020-06-03  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  7:24 Philip Li [this message]
2020-06-03  7:24 ` [0-Day CI notification] kbuild test robot will be combined with kernel test robot Philip Li
2020-06-03  7:24 ` Philip Li

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=20200603072413.GA29050@intel.com \
    --to=philip.li@intel.com \
    --cc=lkp@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.