Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: andriy.shevchenko@linux.intel.com <andriy.shevchenko@linux.intel.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 00/62] Add definition for GPIO direction
Date: Tue, 5 Nov 2019 17:17:42 +0200	[thread overview]
Message-ID: <20191105151742.GU32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191105145946.2ye6ujvqzn2d6fqd@pengutronix.de>

On Tue, Nov 05, 2019 at 03:59:46PM +0100, Uwe Kleine-K?nig wrote:
> On Tue, Nov 05, 2019 at 02:00:02PM +0000, Vaittinen, Matti wrote:
> > On Tue, 2019-11-05 at 14:36 +0100, Uwe Kleine-K?nig wrote:
> > Thanks Uwe! That was kind! I'm on Fedora but I guess I can find the
> > multiarch binutils :) I'll try that tomorrow when I'm back at the
> > office. Let's see what kind of results I can get from it.
> > 
> > Unfortunately bunch of the GPIOs depend on x86 - so I need to see what
> > I can compile in with decent effort. For my compile test I just hacked
> > the Makefile to force all in and added some dummy macros to fix few
> > missing functions :| But I guess I can get some results.
> 
> Enable CONFIG_COMPILE_TEST and then you should be able to compile most
> drivers also on the wrong architecture.

*Wrong* is a wrong word here. I guess you misspelled *another* / *not native*.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2019-11-05 15:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 10:09 [PATCH 00/62] Add definition for GPIO direction Matti Vaittinen
2019-11-05 10:42 ` [PATCH 62/62] gpiolib: Nag for INPUT direction values other than GPIO_LINE_DIRECTION_IN Matti Vaittinen
2019-11-05 10:54 ` [PATCH 00/62] Add definition for GPIO direction Vaittinen, Matti
2019-11-05 12:20 ` Andy Shevchenko
2019-11-05 12:54   ` Vaittinen, Matti
2019-11-05 13:10     ` Uwe Kleine-König
2019-11-05 13:30       ` Vaittinen, Matti
2019-11-05 13:36         ` Uwe Kleine-König
2019-11-05 14:00           ` Vaittinen, Matti
2019-11-05 14:59             ` Uwe Kleine-König
2019-11-05 15:06               ` Vaittinen, Matti
2019-11-05 15:17               ` andriy.shevchenko [this message]
2019-11-05 13:30       ` andriy.shevchenko
2019-11-05 13:40         ` Uwe Kleine-König
2019-11-05 14:28           ` andriy.shevchenko
2019-11-05 13:11     ` andriy.shevchenko
2019-11-05 13:54       ` Vaittinen, Matti
2019-11-05 14:32         ` andriy.shevchenko
2019-11-05 13:10 ` [RESEND PATCH 01/62] gpio: " Matti Vaittinen

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=20191105151742.GU32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-aspeed@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox