netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
	"David S. Miller" <davem@davemloft.net>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Wang Chen <wangchen@cn.fujitsu.com>,
	linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] trivial: fix typo s/refference/reference/ in comment
Date: Fri, 16 Oct 2009 18:08:17 +0200	[thread overview]
Message-ID: <1255709297.31260.2.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.2.00.0910161524480.8582@wotan.suse.de>

Hi Jiri,

> On Thu, 15 Oct 2009, Thadeu Lima de Souza Cascardo wrote:
> 
> > diff --git a/net/bluetooth/bnep/core.c b/net/bluetooth/bnep/core.c
> > index cafe9f5..1bd9398 100644
> > --- a/net/bluetooth/bnep/core.c
> > +++ b/net/bluetooth/bnep/core.c
> > @@ -78,7 +78,7 @@ static struct bnep_session *__bnep_get_session(u8 *dst)
> >  static void __bnep_link_session(struct bnep_session *s)
> >  {
> >  	/* It's safe to call __module_get() here because sessions are added
> > -	   by the socket layer which has to hold the refference to this module.
> > +	   by the socket layer which has to hold the reference to this module.
> >  	 */
> >  	__module_get(THIS_MODULE);
> >  	list_add(&s->list, &bnep_session_list);
> 
> Merged together with patches 2-8 from your series and applied to trivial
> queue.

trivial, but neverless ...

Acked-by: Marcel Holtmann <marcel@holtmann.org>

Regards

Marcel



      reply	other threads:[~2009-10-16 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 20:16 [PATCH 6/8] trivial: fix typo s/refference/reference/ in comment Thadeu Lima de Souza Cascardo
     [not found] ` <1255637783-6109-1-git-send-email-cascardo-DmMZpsCg3uxeGPcbtGPokg@public.gmane.org>
2009-10-16 13:25   ` Jiri Kosina
2009-10-16 16:08     ` Marcel Holtmann [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=1255709297.31260.2.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=cascardo@holoscopio.com \
    --cc=davem@davemloft.net \
    --cc=jkosina@suse.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=wangchen@cn.fujitsu.com \
    /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).