From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Hansjoerg Lipp <hjlipp@web.de>,
Karsten Keil <isdn@linux-pingi.de>,
gigaset307x-common@lists.sourceforge.net, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] isdn/gigaset: off by one check leading to oops
Date: Fri, 18 Jan 2013 15:26:46 +0300 [thread overview]
Message-ID: <20130118122646.GM4584@mwanda> (raw)
In-Reply-To: <50F93D78.5010903@imap.cc>
On Fri, Jan 18, 2013 at 01:18:00PM +0100, Tilman Schmidt wrote:
> I'll prepare a patch of my own, citing you as reporter, if that's
> ok with you.
>
That sounds great.
regards,
dan carpenter
prev parent reply other threads:[~2013-01-18 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 7:44 [patch] isdn/gigaset: off by one check leading to oops Dan Carpenter
2013-01-18 12:18 ` Tilman Schmidt
2013-01-18 12:26 ` 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=20130118122646.GM4584@mwanda \
--to=dan.carpenter@oracle.com \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=hjlipp@web.de \
--cc=isdn@linux-pingi.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tilman@imap.cc \
/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).