On Wed, 2012-08-01 at 12:14 -0400, Paul Gortmaker wrote:
> Normally a single patch doesn't warrant a 0/1, but Liang did some
> digging on this problem and came up with important background, and
> several possible solutions, so I wanted to capture what he'd learned.
>
> The issues with creating an
[Re: [RFC/PATCH 0/1] Fix inability to configure adhoc in 3.4.x] On 01/08/2012
(Wed 19:42) Johannes Berg wrote:
> On Wed, 2012-08-01 at 13:38 -0400, Paul Gortmaker wrote:
>
> > > > 1) cherry pick 8e8b41f9d, and all the driver specific changes it
> > > > requires
On Wed, 2012-08-01 at 13:38 -0400, Paul Gortmaker wrote:
> > > 1) cherry pick 8e8b41f9d, and all the driver specific changes it requires
> > >
> > > 2) make a sub-commit for stable that just takes the total==1 from #1.
> > >
> > > 3) patch iwlwifi/iwl-mac80211.c and add ".types =
> > > BIT(NL80
[Re: [RFC/PATCH 0/1] Fix inability to configure adhoc in 3.4.x] On 01/08/2012
(Wed 18:31) Johannes Berg wrote:
> On Wed, 2012-08-01 at 12:14 -0400, Paul Gortmaker wrote:
>
> [...]
>
> > However, things still weren't right unless he also cherry picked the
> > 8e8b4
On Wed, 2012-08-01 at 12:14 -0400, Paul Gortmaker wrote:
[...]
> However, things still weren't right unless he also cherry picked the
> 8e8b41f9d8c8e6 ("cfg80211: enforce lack of interface combinations")
> to get the later mentioned "total == 1" check within, so that we
> avoid the EBUSY above.
Normally a single patch doesn't warrant a 0/1, but Liang did some
digging on this problem and came up with important background, and
several possible solutions, so I wanted to capture what he'd learned.
The issues with creating an ad-hoc network started in 3.4.3 with the
cherry pick of 463454b5dbd
