From: Ian Campbell <Ian.Campbell@citrix.com>
To: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>
Cc: Brendan Cully <brendan@cs.ubc.ca>,
xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: RFC: Still TODO for 4.2?
Date: Thu, 19 Jan 2012 21:39:11 +0000 [thread overview]
Message-ID: <1327009151.21391.21.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CAP8mzPNVJ32ypc65qVXBbkVFzXnEgfohYqj4S=zR_D-Y6BZLdw@mail.gmail.com>
On Thu, 2012-01-19 at 21:30 +0000, Shriram Rajagopalan wrote:
> On Thu, Jan 19, 2012 at 1:10 PM, Ian Campbell
> Debian has libnl{1,2,3} pacakges in it -- why not use them?
>
>
> Yes I know. I have toyed with them. The qdisc names are hardcoded in
> their libraries. So, even if one installs sch_plug (qdisc name
> "plug"), the library wont recognize it! I do have my own version of
> the library (patched) but as you said, I dont want to bundle that
> stuff with xen.
Why don't you send said patch to the libnl upstream? I'm sure once the
kernel module is in they will be interested in such a patch.
> I must have been mistaken then. Why is your module not
> upstream?
>
>
>
> Beats me.
Did you send it more than once?
According to http://patchwork.ozlabs.org/patch/132315/ it is in state
"changes requested". There is a longish thread attached to the posting
so I assume it is something in there.
Just like with submitting patches to Xen you need to address any review
comments and resend patches, ping people etc, it's not just a case of
firing and forgetting a patch on a mailing list.
Ian.
next prev parent reply other threads:[~2012-01-19 21:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 9:09 RFC: Still TODO for 4.2? Jan Beulich
2012-01-19 16:35 ` Jan Beulich
2012-01-19 17:35 ` Shriram Rajagopalan
2012-01-19 17:46 ` Ian Campbell
2012-01-19 19:00 ` Shriram Rajagopalan
2012-01-19 20:42 ` Konrad Rzeszutek Wilk
2012-01-19 21:25 ` Shriram Rajagopalan
2012-01-19 21:10 ` Ian Campbell
2012-01-19 21:30 ` Shriram Rajagopalan
2012-01-19 21:39 ` Ian Campbell [this message]
[not found] <mailman.456.1326725042.1471.xen-devel@lists.xensource.com>
2012-01-16 15:12 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 16:29 Ian Campbell
2012-01-04 16:47 ` Konrad Rzeszutek Wilk
2012-01-04 16:51 ` Stefano Stabellini
2012-01-16 13:42 ` Ian Campbell
2012-01-04 16:55 ` Jan Beulich
2012-01-16 13:39 ` Ian Campbell
2012-01-16 14:48 ` Jan Beulich
2012-01-16 15:00 ` Stefano Stabellini
2012-01-04 17:25 ` Pasi Kärkkäinen
2012-01-04 17:36 ` George Dunlap
2012-01-04 18:20 ` Tim Deegan
2012-01-05 10:39 ` Ian Campbell
2012-01-04 19:21 ` Wei Huang
2012-01-04 19:43 ` Pasi Kärkkäinen
2012-01-04 19:57 ` Wei Huang
2012-01-05 7:27 ` Pasi Kärkkäinen
2012-01-06 15:37 ` Konrad Rzeszutek Wilk
2012-01-06 19:08 ` Wei Huang
2012-02-06 17:57 ` Pasi Kärkkäinen
2012-01-05 13:19 ` Re : " David TECHER
2012-01-05 13:25 ` Ian Campbell
2012-01-05 13:41 ` Re : " David TECHER
2012-01-05 16:18 ` Ian Campbell
2012-01-16 13:28 ` Ian Campbell
2012-01-04 17:39 ` Roger Pau Monné
2012-01-05 17:49 ` Ian Jackson
2012-01-06 13:37 ` Ian Campbell
2012-01-10 16:06 ` Ian Jackson
2012-01-16 11:55 ` George Dunlap
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=1327009151.21391.21.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=brendan@cs.ubc.ca \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).