From: Jamal Hadi Salim <jhs@mojatatu.com>
To: David Miller <davem@davemloft.net>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Fwd: Re: [PATCH v2 net-next 0/3] net sched action timestamp improvements
Date: Fri, 17 Jun 2016 07:15:27 -0400 [thread overview]
Message-ID: <5763DBCF.9080203@mojatatu.com> (raw)
In-Reply-To: <20160607.155405.778592531194331404.davem@davemloft.net>
Ok, mystery solved. Dave, this patch series is missing from current
net-next.
cheers,
jamal
-------- Forwarded Message --------
Subject: Re: [PATCH v2 net-next 0/3] net sched action timestamp improvements
Date: Tue, 07 Jun 2016 15:54:05 -0700 (PDT)
From: David Miller <davem@davemloft.net>
To: jhs@mojatatu.com
CC: netdev@vger.kernel.org, xiyou.wangcong@gmail.com, daniel@iogearbox.net
From: Jamal Hadi Salim <jhs@mojatatu.com>
Date: Mon, 6 Jun 2016 06:32:52 -0400
> From: Jamal Hadi Salim <jhs@mojatatu.com>
>
> Various aggregations of duplicated code, fixes and introduction of firstused
> timestamp
>
> v2: add const for source time info per suggestion from Cong
Series applied.
next prev parent reply other threads:[~2016-06-17 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 10:32 [PATCH v2 net-next 0/3] net sched action timestamp improvements Jamal Hadi Salim
2016-06-06 10:32 ` [PATCH v2 net-next 1/3] net sched: actions use tcf_lastuse_update for consistency Jamal Hadi Salim
2016-06-06 10:32 ` [PATCH v2 net-next 2/3] net sched actions: introduce timestamp for firsttime use Jamal Hadi Salim
2016-06-06 10:32 ` [PATCH v2 net-next 3/3] net sched actions: aggregate dumping of actions timeinfo Jamal Hadi Salim
2016-06-06 17:37 ` [PATCH v2 net-next 0/3] net sched action timestamp improvements Cong Wang
2016-06-07 22:54 ` David Miller
2016-06-17 11:15 ` Jamal Hadi Salim [this message]
2016-06-18 4:31 ` David Miller
2016-06-18 13:46 ` Jamal Hadi Salim
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=5763DBCF.9080203@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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.