public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: hostapd 2.7 - patches still needed?
Date: Tue, 05 Mar 2019 18:36:35 +0100	[thread overview]
Message-ID: <c573a337-a89a-b67f-f847-d7d42f47c9e5@ipfire.org> (raw)
In-Reply-To: <e5798369857ddf682dd53fe2e3c994a3@ipfire.org>

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

Hi,

On 05.03.2019 12:32, Arne Fitzenreiter wrote:
> On 2019-03-04 13:50, Matthias Fischer wrote:
>> Hi,
>> 
>> can anyone tell me if the 'rebased-v2.6...'-patches for 'hostapd 2.6'
>> are still needed in 'hostapd 2.7'?
>> 
>> I made a quick testrun and most of them answer with "Reversed (or
>> previously applied) patch detected!"
>> 
>> As I see it, 'hostapd-2.6-noscan.patch' should probably stay, line
>> numbers would have to be adjusted.
> This patch is needed for disabling the neighborhood scan to force HT40 
> modes.

Ok - I kept this and the other patch below.

>> 
>> The same applies to 'hostapd-2.3_increase_EAPOL-timeouts.patch'.
> This is needed for some buggy android clients that neet too long to 
> wakeup so it should also stay.

Oh, I see. Adjusted. Applied.

> The others should be rebased from the hostapd/wpa_supplicant tree and 
> included in the new version.
> Please update also wpa_supplicant if hostapd is updated, they should 
> have matching versions.

I noticed that => BTDT already. ;-)

I'll sent patches for both so you can take a look. Both - 'hostapd 2.7'
and 'wpa_supplicant 2.7' - were built tonight without errors.


Best,
Matthias

      reply	other threads:[~2019-03-05 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 12:50 Matthias Fischer
2019-03-05  9:36 ` Michael Tremer
2019-03-05 17:30   ` Matthias Fischer
2019-03-05 18:19   ` Matthias Fischer
2019-03-05 11:32 ` Arne Fitzenreiter
2019-03-05 17:36   ` Matthias Fischer [this message]

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=c573a337-a89a-b67f-f847-d7d42f47c9e5@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.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