public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Toshiaki Makita <makita.toshiaki@lab•ntt.co.jp>
To: "David S . Miller" <davem@davemloft•net>
Cc: Toshiaki Makita <toshiaki.makita1@gmail•com>,
	Patrick McHardy <kaber@trash•net>,
	Stephen Hemminger <stephen@networkplumber•org>,
	Vlad Yasevich <vyasevich@gmail•com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
	intel-wired-lan@lists•osuosl.org, netdev@vger•kernel.org,
	jacob.e.keller@intel•com
Subject: Re: [PATCH net-next 0/4] Automatic adjustment of max frame size
Date: Mon, 26 Oct 2015 09:56:19 +0900	[thread overview]
Message-ID: <562D7A33.4020603@lab.ntt.co.jp> (raw)
In-Reply-To: <562B4673.7020608@gmail.com>

On 2015/10/24 17:50, Toshiaki Makita wrote:
> David,
> 
> I found my patch set is marked with Changes Requested, but I haven't
> seen any feedback.
> 
> Could you give me your feedback?

Somehow the mail from LD Linux CI Server did not reach netdev mailing
list so I could not have seen it from gmail...

Toshiaki Makita

  reply	other threads:[~2015-10-26  0:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  3:49 [PATCH net-next 0/4] Automatic adjustment of max frame size Toshiaki Makita
2015-10-23  3:49 ` [PATCH net-next 1/4] net: Add ndo_enc_hdr_len to notify extra header room for encapsulated frames Toshiaki Makita
2015-10-23  3:49 ` [PATCH net-next 2/4] e1000e: Add ndo_enc_hdr_len Toshiaki Makita
2015-10-23  3:49 ` [PATCH net-next 3/4] vlan: Notify real device of encap header length Toshiaki Makita
2015-10-23  3:49 ` [PATCH net-next 4/4] bridge: Notify port " Toshiaki Makita
2015-10-24  8:50 ` [PATCH net-next 0/4] Automatic adjustment of max frame size Toshiaki Makita
2015-10-26  0:56   ` Toshiaki Makita [this message]
2015-10-26 20:50     ` Keller, Jacob E
2015-10-27  0:40       ` David Miller

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=562D7A33.4020603@lab.ntt.co.jp \
    --to=makita.toshiaki@lab$(echo .)ntt.co.jp \
    --cc=davem@davemloft$(echo .)net \
    --cc=intel-wired-lan@lists$(echo .)osuosl.org \
    --cc=jacob.e.keller@intel$(echo .)com \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=kaber@trash$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stephen@networkplumber$(echo .)org \
    --cc=toshiaki.makita1@gmail$(echo .)com \
    --cc=vyasevich@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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