From: David Miller <davem@davemloft.net>
To: jpirko@redhat.com
Cc: netdev@vger.kernel.org, fubar@us.ibm.com,
bonding-devel@lists.sourceforge.net, monis@voltaire.com
Subject: Re: [PATCH net-next-2.6] bonding: move slave MTU handling from sysfs V2
Date: Wed, 02 Jun 2010 03:40:34 -0700 (PDT) [thread overview]
Message-ID: <20100602.034034.146365447.davem@davemloft.net> (raw)
In-Reply-To: <20100518154016.GD2878@psychotron.lab.eng.brq.redhat.com>
From: Jiri Pirko <jpirko@redhat.com>
Date: Tue, 18 May 2010 17:42:40 +0200
> V1->V2: corrected res/ret use
>
> For some reason, MTU handling (storing, and restoring) is taking place in
> bond_sysfs. The correct place for this code is in bond_enslave, bond_release.
> So move it there.
>
> Signed-off-by: Jiri Pirko <jpirko@redhat.com>
Applied.
prev parent reply other threads:[~2010-06-02 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:42 [PATCH net-next-2.6] bonding: move slave MTU handling from sysfs V2 Jiri Pirko
2010-05-20 0:07 ` Jay Vosburgh
2010-05-20 5:34 ` Jiri Pirko
2010-05-20 18:21 ` Jay Vosburgh
2010-06-02 10:40 ` David Miller [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=20100602.034034.146365447.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=jpirko@redhat.com \
--cc=monis@voltaire.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).