netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org, Alexander Duyck <alexander.h.duyck@intel.com>
Subject: Re: [PATCH 1/2] iproute2 skbedit: Fix help message
Date: Sat, 26 Dec 2009 16:12:46 -0500	[thread overview]
Message-ID: <1261861966.3363.0.camel@bigi> (raw)
In-Reply-To: <20091226110748.2a76660d@nehalam>

On Sat, 2009-12-26 at 11:07 -0800, Stephen Hemminger wrote:
> On Thu, 03 Dec 2009 08:27:24 -0500
> jamal <hadi@cyberus.ca> wrote:
> 
> > 
> > Currently the help text for skbedit implies you can either pass queue
> > mapping or priority. Truth is you can pass both
> > 
> > cheers,
> > jamal
> > 
> applied to 2.6.32 version

It is not in the 2.6.32 release - but seems harmless enough it can stay
in later versions.

cheers,
jamal


      reply	other threads:[~2009-12-26 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 13:27 [PATCH 1/2] iproute2 skbedit: Fix help message jamal
2009-12-26 19:07 ` Stephen Hemminger
2009-12-26 21:12   ` jamal [this message]

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=1261861966.3363.0.camel@bigi \
    --to=hadi@cyberus.ca \
    --cc=alexander.h.duyck@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).