All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jean Delvare <jdelvare@suse.de>,
	"Wu, Fengguang" <fengguang.wu@intel.com>
Subject: Re: [PATCH] i2c: move acpi code back into the core
Date: Wed, 24 Sep 2014 17:44:58 +0200	[thread overview]
Message-ID: <20140924154457.GB1283@katana> (raw)
In-Reply-To: <542139E6.2030806@intel.com>

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

> Hi Wolfram:
> The patch passed through the following 110 configure build test in the
> 0-day build test system.

Thanks, but my tree gets checked automatically anyhow. What I'd need is
functional tests because I don't have hardware to test.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-24 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 21:06 [PATCH] i2c: move acpi code back into the core Wolfram Sang
     [not found] ` <1411420006-4713-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2014-09-23  1:37   ` Lan Tianyu
2014-09-23  1:37     ` Lan Tianyu
     [not found]     ` <5420CEC9.1030400-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-23  5:39       ` Wolfram Sang
2014-09-23  5:39         ` Wolfram Sang
2014-09-23  7:09         ` Lan Tianyu
2014-09-23  7:09           ` Lan Tianyu
2014-09-23  9:14           ` Lan Tianyu
2014-09-24 15:44             ` Wolfram Sang [this message]
2014-09-23  9:14   ` Mika Westerberg
2014-09-23  9:14     ` Mika Westerberg
2014-09-24 15:44     ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2014-09-22 21:03 Wolfram Sang

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=20140924154457.GB1283@katana \
    --to=wsa@the-dreams.de \
    --cc=fengguang.wu@intel.com \
    --cc=jdelvare@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tianyu.lan@intel.com \
    /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.