netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atm: firestream: remove duplicate define
Date: Mon, 21 Oct 2013 07:53:35 -0400	[thread overview]
Message-ID: <20131021075335.5c9e4490@thirdoffive.cmf.nrl.navy.mil> (raw)
In-Reply-To: <1382343161-3243-1-git-send-email-michael.opdenacker@free-electrons.com>

Acked-by: Chas Williams <chas@cmf.nrl.navy.mil>

On Mon, 21 Oct 2013 10:12:41 +0200
Michael Opdenacker <michael.opdenacker@free-electrons.com> wrote:

> This patch removes a duplicate define in drivers/atm/firestream.h
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
> ---
>  drivers/atm/firestream.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/drivers/atm/firestream.h b/drivers/atm/firestream.h
> index 49e783e..364eded 100644
> --- a/drivers/atm/firestream.h
> +++ b/drivers/atm/firestream.h
> @@ -420,7 +420,6 @@ struct fs_transmit_config {
>  #define RC_FLAGS_BFPS_BFP27 (0xd << 17)
>  #define RC_FLAGS_BFPS_BFP47 (0xe << 17)
>  
> -#define RC_FLAGS_BFPS       (0x1 << 17)
>  #define RC_FLAGS_BFPP       (0x1 << 21)
>  #define RC_FLAGS_TEVC       (0x1 << 22)
>  #define RC_FLAGS_TEP        (0x1 << 23)

  reply	other threads:[~2013-10-21 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21  8:12 [PATCH] atm: firestream: remove duplicate define Michael Opdenacker
2013-10-21 11:53 ` chas williams - CONTRACTOR [this message]
2013-10-21 22:47   ` 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=20131021075335.5c9e4490@thirdoffive.cmf.nrl.navy.mil \
    --to=chas@cmf.nrl.navy.mil \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.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).