On Sun, Feb 17, 2019 at 12:15:39PM -0800, akuster808 wrote:
>
>
> On 2/15/19 5:13 PM, Tom Rini wrote:
> > On Fri, Feb 15, 2019 at 10:46:13AM -0500, Bruce Ashfield wrote:
> >
> >> merged.
> >>
> >> SRCREV updates will be sent out with my next queue.
> > Thanks. What's the backport policy here? I
On 2/15/19 5:13 PM, Tom Rini wrote:
> On Fri, Feb 15, 2019 at 10:46:13AM -0500, Bruce Ashfield wrote:
>
>> merged.
>>
>> SRCREV updates will be sent out with my next queue.
> Thanks. What's the backport policy here? I first ran into this issue
> back on Jethro (but that's a fair bit too far to
On Fri, Feb 15, 2019 at 10:46:13AM -0500, Bruce Ashfield wrote:
> merged.
>
> SRCREV updates will be sent out with my next queue.
Thanks. What's the backport policy here? I first ran into this issue
back on Jethro (but that's a fair bit too far to expect a backport to)
and I finally root cause
merged.
SRCREV updates will be sent out with my next queue.
Bruce
On Tue, Feb 12, 2019 at 2:10 PM Tom Rini wrote:
>
> In order for logging to work, as for example seen with the default
> configuration of 'ufw' we need to have logging support enabled. This is
> currently gated on the CONFIG_NET
In order for logging to work, as for example seen with the default
configuration of 'ufw' we need to have logging support enabled. This is
currently gated on the CONFIG_NETFILTER_XT_TARGET_LOG option, so enable
it here.
Fixes: f56608b405f0 ("meta: cleanup invalid/obselete 3.4 CONFIG options")
Sig