linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@ring0.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-wireless@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 0/5] wl1251 device tree support
Date: Fri, 24 Jan 2014 22:53:22 +0100	[thread overview]
Message-ID: <20140124215321.GA25727@earth.universe> (raw)
In-Reply-To: <20140118174705.GE7235@atomide.com>

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

On Sat, Jan 18, 2014 at 09:47:06AM -0800, Tony Lindgren wrote:
> [...]
> 
> The reason was for keeping things building and git bisect working.
> 
> I do have wl1251-pdata-signed as the base for branch
> omap-for-v3.14/omap3-board-removal. However the board removal was
> considered too early for v3.14, so that's been postponed. This is
> because people are still updating their systems to device tree
> based booting. So I can redo my omap-for-v3.14/omap3-board-removal
> against v3.14.
> 
> So if you want to, feel free to pick all the wl12xx patches to your
> wireless tree. AFAIK my omap-for-v3.14/omap3-board-removal is the
> only other user for those patches, and that I can redo that on
> v3.14.
> 
> So for the arch/arm/*omap* touching patches, feel free to add:
> 
> Acked-by: Tony Lindgren <tony@atomide.com>

Another ping. If this does not go into 3.14 via wireless tree
it will become complicated for 3.15 again.

-- Sebastian

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

  reply	other threads:[~2014-01-24 21:53 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 16:14 [PATCH 0/4] wl1251 device tree support Sebastian Reichel
2013-10-27 16:14 ` [PATCH 1/4] wl1251: split wl251 platform data to a separate structure Sebastian Reichel
     [not found]   ` <1382890469-25286-2-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-05 12:13     ` Pavel Machek
2013-11-14 18:51   ` Tony Lindgren
2013-11-14 23:03     ` Sebastian Reichel
2013-11-14 23:22       ` Tony Lindgren
2013-11-15 14:32         ` John W. Linville
     [not found]           ` <20131115143254.GA7079-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-11-15 14:55             ` Sebastian Reichel
2013-12-10  3:28           ` Tony Lindgren
2013-10-27 16:14 ` [PATCH 2/4] wl1251: move power GPIO handling into the driver Sebastian Reichel
2013-10-27 16:24   ` Alexander Shiyan
2013-10-27 20:12     ` Sebastian Reichel
2013-10-28 17:29       ` Grazvydas Ignotas
2013-10-28 19:23         ` Mark Brown
2013-10-28 23:26           ` Sebastian Reichel
2013-10-29  1:33             ` Mark Brown
     [not found]   ` <1382890469-25286-3-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-05 13:11     ` Pavel Machek
2013-10-27 16:14 ` [PATCH 3/4] wl1251: spi: add vio regulator support Sebastian Reichel
     [not found]   ` <1382890469-25286-4-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-11-05 13:12     ` Pavel Machek
2013-10-27 16:14 ` [PATCH 4/4] wl1251: spi: add device tree support Sebastian Reichel
2013-10-28  6:37   ` Kumar Gala
2013-10-28 17:15     ` Grazvydas Ignotas
2013-10-28 19:30       ` Kumar Gala
2013-10-28 22:38     ` Tomasz Figa
2013-10-29  8:28       ` Kumar Gala
     [not found] ` <1382890469-25286-1-git-send-email-sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-12-06  0:22   ` [PATCHv2 0/5] wl1251 " Sebastian Reichel
2013-12-06  0:22     ` [PATCHv2 1/5] wl1251: split wl251 platform data to a separate structure Sebastian Reichel
2013-12-06  0:22     ` [PATCHv2 2/5] wl1251: move power GPIO handling into the driver Sebastian Reichel
2013-12-06  0:22     ` [PATCHv2 3/5] wl1251: spi: add vio regulator support Sebastian Reichel
2013-12-06  0:22     ` [PATCHv2 4/5] wl1251: spi: add device tree support Sebastian Reichel
2013-12-06  0:22     ` [PATCHv2 5/5] Documentation: dt: wireless: Add wl1251 Sebastian Reichel
2014-01-06 22:57     ` [PATCHv2 0/5] wl1251 device tree support Sebastian Reichel
     [not found]       ` <20140106225709.GA23070-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2014-01-17  1:45         ` Sebastian Reichel
2014-01-17 15:01           ` John W. Linville
2014-01-17 17:44             ` Tony Lindgren
2014-01-17 19:22               ` John W. Linville
2014-01-18 17:47                 ` Tony Lindgren
2014-01-24 21:53                   ` Sebastian Reichel [this message]
2014-01-24 23:56                     ` John W. Linville
2014-01-25  0:09                       ` Tony Lindgren
2014-02-14 23:05                         ` [RESEND] " Sebastian Reichel
2014-02-14 23:05                           ` [PATCHv2 1/5] wl1251: split wl251 platform data to a separate structure Sebastian Reichel
2014-02-14 23:05                           ` [PATCHv2 2/5] wl1251: move power GPIO handling into the driver Sebastian Reichel
2014-02-14 23:05                           ` [PATCHv2 3/5] wl1251: spi: add vio regulator support Sebastian Reichel
2014-02-14 23:05                           ` [PATCHv2 4/5] wl1251: spi: add device tree support Sebastian Reichel
2014-02-14 23:05                           ` [PATCHv2 5/5] Documentation: dt: wireless: Add wl1251 Sebastian Reichel

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=20140124215321.GA25727@earth.universe \
    --to=sre@ring0.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).