From: Wolfram Sang <wsa@the-dreams.de>
To: Ben Dooks <ben-linux@fluff.org>
Cc: linux-kernel@lists.codethink.co.uk,
linux-amlogic@lists.infradead.org, linux-i2c@vger.kernel.org,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH v2] i2c: meson: allow build with COMPILE_TEST
Date: Fri, 8 Jul 2016 10:39:01 +0900 [thread overview]
Message-ID: <20160708013901.GB10192@tetsubishi> (raw)
In-Reply-To: <1467836225-2427-1-git-send-email-ben-linux@fluff.org>
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
On Wed, Jul 06, 2016 at 09:17:05PM +0100, Ben Dooks wrote:
> This driver should be buildable with COMPILE_TEST so
> add this to the dependency for it.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Care to explain why the first one was better? A bit confused here...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-07-08 1:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 20:17 [PATCH v2] i2c: meson: allow build with COMPILE_TEST Ben Dooks
2016-07-07 8:05 ` Ben Dooks
2016-07-08 1:39 ` Wolfram Sang [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=20160708013901.GB10192@tetsubishi \
--to=wsa@the-dreams.de \
--cc=ben-linux@fluff.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox