On Tue, Jan 22, 2019 at 05:14:05PM -0800, Gregory Rose wrote:
>
> On 1/22/2019 5:09 PM, Ben Pfaff wrote:
> > On Tue, Jan 22, 2019 at 05:08:38PM -0800, Ben Pfaff wrote:
> > > On Tue, Jan 22, 2019 at 04:38:24PM -0800, Yi-Hung Wei wrote:
> > > > On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
> >
On 1/22/2019 5:22 PM, Ben Pfaff wrote:
On Tue, Jan 22, 2019 at 05:14:05PM -0800, Gregory Rose wrote:
On 1/22/2019 5:09 PM, Ben Pfaff wrote:
On Tue, Jan 22, 2019 at 05:08:38PM -0800, Ben Pfaff wrote:
On Tue, Jan 22, 2019 at 04:38:24PM -0800, Yi-Hung Wei wrote:
On Thu, Jan 10, 2019 at 2:09 PM
On 1/22/2019 5:09 PM, Ben Pfaff wrote:
On Tue, Jan 22, 2019 at 05:08:38PM -0800, Ben Pfaff wrote:
On Tue, Jan 22, 2019 at 04:38:24PM -0800, Yi-Hung Wei wrote:
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
how ipv6
On Tue, Jan 22, 2019 at 05:08:38PM -0800, Ben Pfaff wrote:
> On Tue, Jan 22, 2019 at 04:38:24PM -0800, Yi-Hung Wei wrote:
> > On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
> > >
> > > Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
> > > how ipv6 fragmentation is
On Tue, Jan 22, 2019 at 04:38:24PM -0800, Yi-Hung Wei wrote:
> On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
> >
> > Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
> > how ipv6 fragmentation is implemented. This patch was backported to
> > the upstream stable 4.9.x
On 1/22/2019 4:38 PM, Yi-Hung Wei wrote:
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
how ipv6 fragmentation is implemented. This patch was backported to
the upstream stable 4.9.x kernel starting at 4.9.135.
This
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
>
> Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
> how ipv6 fragmentation is implemented. This patch was backported to
> the upstream stable 4.9.x kernel starting at 4.9.135.
>
> This patch creates the compatibility
On 1/21/2019 2:06 PM, Gregory Rose wrote:
It turns out after I had more of a chance to look at this that
HAVE_INET_FRAGS_WITH_FRAGS_WORK and
HAVE_INET_FRAGS_RND are both keying off the same upstream patch I
mentioned in the commit message
(648700f76b03). There's no need for the redundancy.
On 1/14/2019 4:20 PM, Gregory Rose wrote:
On 1/14/2019 3:22 PM, Yi-Hung Wei wrote:
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
Upstream commit 648700f76b03 ("inet: frags: use rhashtables...")
changed
how ipv6 fragmentation is implemented. This patch was backported to
the upstream
On 1/14/2019 3:22 PM, Yi-Hung Wei wrote:
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
how ipv6 fragmentation is implemented. This patch was backported to
the upstream stable 4.9.x kernel starting at 4.9.135.
This
On Thu, Jan 10, 2019 at 2:09 PM Greg Rose wrote:
>
> Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
> how ipv6 fragmentation is implemented. This patch was backported to
> the upstream stable 4.9.x kernel starting at 4.9.135.
>
> This patch creates the compatibility
Upstream commit 648700f76b03 ("inet: frags: use rhashtables...") changed
how ipv6 fragmentation is implemented. This patch was backported to
the upstream stable 4.9.x kernel starting at 4.9.135.
This patch creates the compatibility layer changes required to both
compile and also operate
12 matches
Mail list logo
