From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
brouer@redhat.com
Subject: Re: ADSL/ATM linklayer tc shaping regression fix commits for stable
Date: Thu, 22 Aug 2013 10:04:26 +0200 [thread overview]
Message-ID: <20130822100426.39be319d@redhat.com> (raw)
In-Reply-To: <20130821.112023.744177612387539958.davem@davemloft.net>
On Wed, 21 Aug 2013 11:20:23 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Jesper Dangaard Brouer <brouer@redhat.com>
> Date: Wed, 21 Aug 2013 14:03:50 +0200
>
> >
> > On Tue, 20 Aug 2013 08:16:50 -0700
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >> On Tue, Aug 20, 2013 at 01:26:29PM +0200, Jesper Dangaard Brouer wrote:
> > [...]
> >
> >> If there are issues with 3.10, that's a different story.
> >>
> >> > Refactor improvements (v3.11-rc1):
> >> > commit 130d3d68b52 (net_sched: psched_ratecfg_precompute() improvements)
> >
> > Needed because it fixes the accuracy of the rate calc.
> >
> >> > The linklayer ATM/ADSL fix, reached 3.11-rc6:
> >> > commit 8a8e3d84b17 (net_sched: restore "linklayer atm" handling)
> >
> > Needed because we broke userspace interface.
> >
> >> David sends me the networking patches for the stable tree, and if he
> >> thinks these are applicable, then I'll take them.
> >
> > DaveM, please? What do you want me to do, submit this req/patches somehow?
> >
> > (Can see that is not currently on your stable queue via:
> > http://patchwork.ozlabs.org/bundle/davem/stable/?state=*)
>
> I'll put it there, you just have to formally ask me to do it that's
> all.
Thanks, I assume that this was formally enough and you are taking the patches.
So, for future reference:
Stable patches for the networking tree, I should:
1) check http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
to see if my patch is already on your stable queue
2) if not, ask you and cc netdev@vger.kernel.org
3) you will handle the interaction with Greg and stable@vger.kernel.org
Correct?
> Asking Greg to do it directly is a complete waste of time. :-)
I'll remember that. I was just following Documentation/stable_kernel_rules.txt,
I guess I should have known better as all my previous stable patches
have automagically been picked up and processed by you :-)
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2013-08-22 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 11:26 ADSL/ATM linklayer tc shaping regression fix commits for stable Jesper Dangaard Brouer
2013-08-20 15:16 ` Greg Kroah-Hartman
2013-08-21 12:03 ` Jesper Dangaard Brouer
[not found] ` <20130821140350.2b953007-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-08-21 17:10 ` Dave Taht
2013-08-21 18:20 ` David Miller
2013-08-21 18:20 ` David Miller
2013-08-22 8:04 ` Jesper Dangaard Brouer [this message]
2013-08-22 8:23 ` David Miller
2013-08-22 8:41 ` Jesper Dangaard Brouer
2013-08-23 7:59 ` Li Zefan
2013-08-23 8:09 ` David Miller
2013-08-23 8:01 ` Li Zefan
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=20130822100426.39be319d@redhat.com \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.