From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jonghwan Choi <jhbird.choi@gmail.com>
Cc: Jon Mason <jon.mason@intel.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonghwan Choi <jhbird.choi@samsung.com>
Subject: Re: [PATCH 3.9-table] NTB: fix pointer math issues
Date: Sat, 18 May 2013 13:00:52 +0300 [thread overview]
Message-ID: <20130518100052.GA30128@mwanda> (raw)
In-Reply-To: <1368844745-3908-1-git-send-email-jhbird.choi@samsung.com>
On Sat, May 18, 2013 at 11:39:05AM +0900, Jonghwan Choi wrote:
> From: Dan Carpenter <dan.carpenter@oracle.com>
>
> This patch looks like it should be in the 3.9-stable tree, should we apply
> it?
>
Normally these questions are handled by the subsystem maintainer.
regards,
dan carpenter
next prev parent reply other threads:[~2013-05-18 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 2:39 [PATCH 3.9-table] NTB: fix pointer math issues Jonghwan Choi
2013-05-18 10:00 ` Dan Carpenter [this message]
2013-05-18 11:58 ` jonghwan Choi
2013-05-18 14:49 ` Jon Mason
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=20130518100052.GA30128@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jhbird.choi@gmail.com \
--cc=jhbird.choi@samsung.com \
--cc=jon.mason@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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