public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: Michal Simek <michal.simek@xilinx.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Kevin Hilman <khilman@linaro.org>
Subject: Re: [PATCH 00/11] ARM: multi_v7_defconfig: Enable Zynq/Xilinx drivers
Date: Fri, 22 Aug 2014 21:17:34 -0700	[thread overview]
Message-ID: <20140823041734.GA11268@localhost> (raw)
In-Reply-To: <1408722876-7791-1-git-send-email-soren.brinkmann@xilinx.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1022 bytes --]

On Fri, Aug 22, 2014 at 08:54:25AM -0700, Soren Brinkmann wrote:
> Hi,
> 
> I went through the defconfig and searched for Zynq drivers. The result is
> this series of patches. The first few are all for Zynq and pretty much
> straight forward. The second half is mostly soft-IP, I think. That
> soft-IP works with Zynq devices, but I'm not sure whether those should
> go into the multi_v7 defconfig.

Thanks, SÃren! 

There's no need to split up into individual patches like this, but it was
convenient in case I wanted to only apply a few of them. I took them all
as one patch, and used your series description as commit message since
none of the individual patches had any. :)

As far as "unusual" drivers in the multiconfig; yeah, we need to deal
with that at some point due to kernel size. We're likely to switch ti
using modules first, but it'll make things slightly more complicated
since people will need to start dealing with initrds and at least I
don't have a good setup for that in my test farm yet. :-)


-Olof

  parent reply	other threads:[~2014-08-23  5:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 15:54 [PATCH 00/11] ARM: multi_v7_defconfig: Enable Zynq/Xilinx drivers Soren Brinkmann
2014-08-22 15:54 ` [PATCH 01/11] ARM: multi_v7_defconfig: Enable Zynq cpuidle driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 02/11] ARM: multi_v7_defconfig: Enable Zynq/Xilinx CAN driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 03/11] ARM: multi_v7_defconfig: Enable XADC driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 04/11] ARM: multi_v7_defconfig: Enable Zynq SPI driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 05/11] ARM: multi_v7_defconfig: Enable Zynq GPIO driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 06/11] ARM: multi_v7_defconfig: Enable Xilinx I2C driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 07/11] ARM: multi_v7_defconfig: Enable Xilinx SPI driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 08/11] ARM: multi_v7_defconfig: Enable Xilinx GPIO driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 09/11] ARM: multi_v7_defconfig: Enable Xilinx VDMA driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 10/11] ARM: multi_v7_defconfig: Enable Xilinx emaclite driver Soren Brinkmann
2014-08-22 15:54 ` [PATCH 11/11] ARM: multi_v7_defconfig: Enable Xilinx watchdog timer Soren Brinkmann
2014-08-23  4:17 ` Olof Johansson [this message]
2014-08-25 14:42   ` [PATCH 00/11] ARM: multi_v7_defconfig: Enable Zynq/Xilinx drivers Sören Brinkmann

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=20140823041734.GA11268@localhost \
    --to=olof@lixom.net \
    --cc=arnd@arndb.de \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=soren.brinkmann@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox