Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfeldma@cumulusnetworks.com
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
	roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
	curt@cumulusnetworks.com, shm@cumulusnetworks.com
Subject: Re: [PATCH net-next 2/2] bridge: use DEVICE_ATTR_xx macros
Date: Mon, 06 Jan 2014 16:41:26 -0500 (EST)	[thread overview]
Message-ID: <20140106.164126.1436204419132200005.davem@davemloft.net> (raw)
In-Reply-To: <20140106190044.10912.47228.stgit@monster-03.cumulusnetworks.com>

From: Scott Feldman <sfeldma@cumulusnetworks.com>
Date: Mon, 06 Jan 2014 11:00:44 -0800

> Use DEVICE_ATTR_RO/RW macros to simplify bridge sysfs attribute definitions.
> 
> Signed-off-by: Scott Feldman <sfeldma@cumulusnetworks.com>

Applied to net-next, thanks.

      reply	other threads:[~2014-01-06 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 19:00 [PATCH net-next 2/2] bridge: use DEVICE_ATTR_xx macros Scott Feldman
2014-01-06 21:41 ` 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=20140106.164126.1436204419132200005.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bridge@lists.linux-foundation.org \
    --cc=curt@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sfeldma@cumulusnetworks.com \
    --cc=shm@cumulusnetworks.com \
    --cc=stephen@networkplumber.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