linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Ian Abbott <abbotti@mev.co.uk>,
	devel@driverdev.osuosl.org,
	Mori Hess <fmhess@users.sourceforge.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging/comedi: Fix undefined array subscript
Date: Wed, 13 Feb 2013 17:58:56 +0300	[thread overview]
Message-ID: <20130213145856.GB4606@mwanda> (raw)
In-Reply-To: <1360765694-3748-1-git-send-email-peterhuewe@gmx.de>

Looks great.  :)  Thanks for fixing this bug.

regards,
dan


      reply	other threads:[~2013-02-13 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13  3:30 [PATCH] staging/comedi: Fix undefined array subscript Peter Huewe
2013-02-13  7:32 ` Dan Carpenter
2013-02-13 11:56   ` Ian Abbott
2013-02-13 13:47     ` Ian Abbott
2013-02-13 14:01       ` Dan Carpenter
2013-02-13 14:28         ` [PATCH v2] " Peter Huewe
2013-02-13 14:58           ` Dan Carpenter [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=20130213145856.GB4606@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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).