netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: netdev@vger.kernel.org
Cc: linux-atm-general@lists.sourceforge.net
Subject: Re: [PATCH 1/1] Use VPI.VCI notation consistently in solos-pci driver
Date: Sun, 26 Dec 2010 12:13:33 -0800	[thread overview]
Message-ID: <4D17A1ED.4080601@redfish-solutions.com> (raw)
In-Reply-To: <4D1792D1.4040803@redfish-solutions.com>

Nix.

My sed script mangled the paths, and after doing a quick check on git.kernel.org I see this one has already been applied... it just hasn't made it back downstream into the openadsl project on SourceForge.


On 12/26/10 11:09 AM, Philip Prindeville wrote:
> Use VPI.VCI notation consistently.
>
> Signed-of-by: Philip Prindeville<philipp@redfish-solutions.com>
> ---
>
> --- a/drivers/atm/solos-pci-0.11/solos-pci.c    2010-12-24 01:07:09.000000000 -0700
> +++ b/drivers/atm/solos-pci-0.11/solos-pci.c    2010-12-24 14:18:45.000000000 -0700
> @@ -734,8 +734,8 @@ void solos_bh(unsigned long card_arg)
>                             le16_to_cpu(header->vci));
>                  if (!vcc) {
>                      if (net_ratelimit())
> -                        dev_warn(&card->dev->dev, "Received packet for unknown VCI.VPI %d.%d on port %d\n",
> -                             le16_to_cpu(header->vci), le16_to_cpu(header->vpi),
> +                        dev_warn(&card->dev->dev, "Received packet for unknown VPI.VCI %d.%d on port %d\n",
> +                             le16_to_cpu(header->vpi), le16_to_cpu(header->vci),
>                               port);
>                      continue;
>                  }
>
>


      reply	other threads:[~2010-12-26 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-26 19:09 [PATCH 1/1] Use VPI.VCI notation consistently in solos-pci driver Philip Prindeville
2010-12-26 20:13 ` Philip Prindeville [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=4D17A1ED.4080601@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --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).