linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: 3chas3@gmail.com, linux-atm-general@lists.sourceforge.net,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: atm: eni: rename macro DAUGTHER_ID to fix spelling mistake
Date: Thu, 29 Dec 2016 12:07:13 -0500 (EST)	[thread overview]
Message-ID: <20161229.120713.1312564302312568056.davem@davemloft.net> (raw)
In-Reply-To: <20161228173120.20207-1-colin.king@canonical.com>

From: Colin King <colin.king@canonical.com>
Date: Wed, 28 Dec 2016 17:31:20 +0000

> From: Colin Ian King <colin.king@canonical.com>
> 
> Rename DAUGTHER_ID to DAUGHTER_ID to fix spelling mistake
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Applied.

      reply	other threads:[~2016-12-29 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 17:31 [PATCH] drivers: atm: eni: rename macro DAUGTHER_ID to fix spelling mistake Colin King
2016-12-29 17:07 ` 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=20161229.120713.1312564302312568056.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=3chas3@gmail.com \
    --cc=colin.king@canonical.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).