From: linville@tuxdriver.com (John W. Linville)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] wl1251: split wl251 platform data to a separate structure
Date: Fri, 15 Nov 2013 09:32:55 -0500 [thread overview]
Message-ID: <20131115143254.GA7079@tuxdriver.com> (raw)
In-Reply-To: <20131114232217.GV10317@atomide.com>
On Thu, Nov 14, 2013 at 03:22:18PM -0800, Tony Lindgren wrote:
> * Sebastian Reichel <sre@debian.org> [131114 15:04]:
> > On Thu, Nov 14, 2013 at 10:51:33AM -0800, Tony Lindgren wrote:
> > > [...]
> > >
> > > If this is not going into v3.13, these will cause conflicts
> > > with the mach-omap2/board-*.c files for v3.14.
> > >
> > > So it might be best to do a minimal header patch first that
> > > can be merged in by both linux-omap and wireless trees.
> >
> > I guess this patch is pretty minimal. It also seems to be acked by
> > the involved Maintainers, so maybe just merge Patch 1 without the
> > other patches?
> >
> > This does not solve the problem with the struct modification from
> > the second patch, but I guess it's the more intrusive patch.
>
> Once at least the first two patches are ready, how about I queue
> them after -rc1 and set up an immutable branch that can be merged
> in by linux-omap tree and the wireless tree?
That sounds reasonable to me.
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-11-15 14:32 UTC|newest]
Thread overview: 25+ 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
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 [this message]
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
2013-11-05 13:11 ` Pavel Machek
2013-10-27 16:14 ` [PATCH 3/4] wl1251: spi: add vio regulator support Sebastian Reichel
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
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=20131115143254.GA7079@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).