From: Dan Carpenter <dan.carpenter@oracle.com>
To: Quentin Lambert <lambert.quentin@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] staging: vt6655: remove deprecated use of pci api
Date: Fri, 20 Mar 2015 16:13:10 +0300 [thread overview]
Message-ID: <20150320131310.GX10964@mwanda> (raw)
In-Reply-To: <1426856800-10920-1-git-send-email-lambert.quentin@gmail.com>
Use the --in-reply-to option. There were no responses to the first
version of this email so Greg is going to apply that one. (I guess it's
still possible that someone will reply to it now, I suppose).
> ---
> Changes since v1:
> - Replaces GFP_ATOMIC by GFP_KERNEL since no lock is taken before calling
> this function
This information about the locking should go in the commit message and
not under the cut-off.
regards,
dan carpenter
prev parent reply other threads:[~2015-03-20 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 13:06 [PATCH v2] staging: vt6655: remove deprecated use of pci api Quentin Lambert
2015-03-20 13:13 ` 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=20150320131310.GX10964@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lambert.quentin@gmail.com \
--cc=linux-kernel@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