linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stefan@agner.ch
Cc: shc_work@mail.ru, jarod@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: cx89x0: move attribute declaration before struct keyword
Date: Tue, 18 Apr 2017 16:00:46 -0400 (EDT)	[thread overview]
Message-ID: <20170418.160046.2007615902301910021.davem@davemloft.net> (raw)
In-Reply-To: <20170417205434.12663-1-stefan@agner.ch>

From: Stefan Agner <stefan@agner.ch>
Date: Mon, 17 Apr 2017 13:54:34 -0700

> The attribute declaration is typically before the definition. Move
> the __maybe_unused attribute declaration before the struct keyword.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> Changes in v2:
> - Move __maybe_unused after the complete type

Applied to net-next, thank you.

      reply	other threads:[~2017-04-18 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 20:54 [PATCH v2] net: cx89x0: move attribute declaration before struct keyword Stefan Agner
2017-04-18 20:00 ` 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=20170418.160046.2007615902301910021.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jarod@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shc_work@mail.ru \
    --cc=stefan@agner.ch \
    /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).