netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] ravb: minimize TX data copying
Date: Sat, 25 Jul 2015 22:40:37 +0200	[thread overview]
Message-ID: <20150725204037.GA2172@nanopsycho.fritz.box> (raw)
In-Reply-To: <7692456.7SI5hJLWyQ@wasted.cogentembedded.com>

Sat, Jul 25, 2015 at 09:20:30PM CEST, sergei.shtylyov@cogentembedded.com wrote:

<snip>

>The patch is against Dave Miller's 'net-next.git' repo.

You can just put "net-next" into patch brackets like:
[patch net-next] whatever
That would do the trick :)

  reply	other threads:[~2015-07-25 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 19:20 [PATCH] ravb: minimize TX data copying Sergei Shtylyov
2015-07-25 20:40 ` Jiri Pirko [this message]
2015-07-25 20:49   ` Sergei Shtylyov

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=20150725204037.GA2172@nanopsycho.fritz.box \
    --to=jiri@resnulli.us \
    --cc=linux-sh@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).