From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David L Stevens <david.stevens@oracle.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCHv5 net-next 0/3] sunvnet: add jumbo frames support
Date: Wed, 17 Sep 2014 18:33:24 -0400 [thread overview]
Message-ID: <20140917223324.GK26828@oracle.com> (raw)
In-Reply-To: <5419F3DC.60104@oracle.com>
>
> arch/sparc/include/asm/vio.h | 44 ++++++++++-
> arch/sparc/kernel/ldc.c | 2 +-
> arch/sparc/kernel/viohs.c | 14 +++-
> drivers/net/ethernet/sun/sunvnet.c | 146 +++++++++++++++++++++++++++++++-----
> drivers/net/ethernet/sun/sunvnet.h | 7 ++-
> 5 files changed, 187 insertions(+), 26 deletions(-)
>
A logistical question- this patch-set spans both sparc-next/sparclinux
net-next/netdev, and there are obviously some dependancies here.
What's the prescribed way to handle this sort of thing?
(I ask, because I expect to soon be confronting a similar question with
some Rx side latency improvements that I'm working on, which will require
new functions for enabling/disabling interrupts in arch/sparc/kernel,
and I am wondering how that should get sequenced).
--Sowmini
prev parent reply other threads:[~2014-09-17 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 20:49 [PATCHv5 net-next 0/3] sunvnet: add jumbo frames support David L Stevens
2014-09-17 22:33 ` Sowmini Varadhan [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=20140917223324.GK26828@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--cc=david.stevens@oracle.com \
--cc=netdev@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 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).