From: Alexander Mukhin <alexander.i.mukhin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] hostapd: add support for Realtek driver
Date: Thu, 14 Sep 2017 13:39:48 +0300 [thread overview]
Message-ID: <20170914103948.GC1462@hpx> (raw)
In-Reply-To: <20170914102413.mxajoxtjz2shgkx2@tarshish>
Hi Baruch,
On Thu, Sep 14, 2017 at 01:24:13PM +0300, Baruch Siach wrote
> I don't believe anyone looks at the code under (by default) output/build/ for
> options. I think that the Config.in entry is enough. The patch is just a
> maintenance burden, IMO.
Agree on defconfig patch. But the second patch modifies hostapd.conf
which is installed to the target and may be consulted by the user
on the available configuration options.
Anyway, if you think it's not necessary too, then the fewer patches, the
better :)
--
Alexander.
next prev parent reply other threads:[~2017-09-14 10:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 17:11 [Buildroot] Realtek-patched hostapd Alexander Mukhin
2017-09-07 19:54 ` Peter Korsgaard
2017-09-08 11:19 ` Alexander Mukhin
2017-09-11 23:14 ` Arnout Vandecappelle
2017-09-14 8:57 ` Alexander Mukhin
2017-09-14 9:00 ` [Buildroot] [PATCH] hostapd: add support for Realtek driver Alexander Mukhin
2017-09-14 9:32 ` Baruch Siach
2017-09-14 10:19 ` Alexander Mukhin
2017-09-14 10:24 ` Baruch Siach
2017-09-14 10:39 ` Alexander Mukhin [this message]
2017-09-14 11:08 ` Alexander Mukhin
2017-11-03 16:17 ` Angelo Compagnucci
2017-11-24 20:58 ` Thomas Petazzoni
2017-11-25 10:32 ` Alexander Mukhin
2017-11-25 10:46 ` Thomas Petazzoni
2017-11-25 11:08 ` [Buildroot] [PATCH] hostapd: keep previous patches when DRIVER_RTW set Alexander Mukhin
2017-11-25 11:18 ` [Buildroot] [PATCH] hostapd: add support for Realtek driver Alexander Mukhin
2017-11-25 10:50 ` Alexander Mukhin
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=20170914103948.GC1462@hpx \
--to=alexander.i.mukhin@gmail.com \
--cc=buildroot@busybox.net \
/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