All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: "David E. Box" <david.e.box-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Mika Westerberg
	<mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	kbuild-all-JC7UmRfGjtg@public.gmane.org
Subject: Re: [PATCH] i2c: designware-baytrail: use proper Kconfig dependencies
Date: Mon, 26 Jan 2015 19:10:43 +0100	[thread overview]
Message-ID: <20150126181043.GC25317@katana> (raw)
In-Reply-To: <20150126180110.GA31916@pathfinder>

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

On Mon, Jan 26, 2015 at 10:01:10AM -0800, David E. Box wrote:
> On Mon, Jan 26, 2015 at 05:49:34PM +0100, Wolfram Sang wrote:
> > IOSF_MBI depends on PCI, so we should not select it but depend on it.
> > This ensures also we compile on X86 only, other archs will break because
> > of an arch specific include. Also depend on ACPI since this driver uses
> > it.
> > 
> > Signed-off-by: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
> 
> Signed-off-by: David E. Box <david.e.box-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

You probably mean Acked-by?


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

  reply	other threads:[~2015-01-26 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:49 [PATCH] i2c: designware-baytrail: use proper Kconfig dependencies Wolfram Sang
     [not found] ` <1422290974-24561-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-01-26 16:51   ` Wolfram Sang
2015-01-26 18:01   ` David E. Box
2015-01-26 18:10     ` Wolfram Sang [this message]
2015-01-26 18:47   ` David E. Box
2015-01-26 21:00   ` Wolfram Sang
2015-01-27 10:17   ` Mika Westerberg

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=20150126181043.GC25317@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=david.e.box-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.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.