From: Scott Wood <swood@redhat.com>
To: Alan Tull <atull@kernel.org>, Moritz Fischer <mdf@kernel.org>
Cc: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
Wu Hao <hao.wu@intel.com>
Subject: Re: [PATCH] fpga: dfl: Add lockdep classes for pdata->lock
Date: Thu, 11 Apr 2019 10:17:21 -0500 [thread overview]
Message-ID: <f0c67ba35e963f61c05421f837bbf6b81be914a7.camel@redhat.com> (raw)
In-Reply-To: <20190410215339.8074-1-swood@redhat.com>
On Wed, 2019-04-10 at 16:53 -0500, Scott Wood wrote:
> @@ -443,11 +450,16 @@ static int build_info_commit_dev(struct
> build_feature_devs_info *binfo)
> struct platform_device *fdev = binfo->feature_dev;
> struct dfl_feature_platform_data *pdata;
> struct dfl_feature_info *finfo, *p;
> + static enum dfl_id_type type;
> int ret, index = 0;
Ugh, not sure how that "static" snuck in there (probably copy-and-paste
error). Will send v2.
-Scott
prev parent reply other threads:[~2019-04-11 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 21:53 [PATCH] fpga: dfl: Add lockdep classes for pdata->lock Scott Wood
2019-04-11 12:43 ` Wu Hao
2019-04-11 15:17 ` Scott Wood [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=f0c67ba35e963f61c05421f837bbf6b81be914a7.camel@redhat.com \
--to=swood@redhat.com \
--cc=atull@kernel.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@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;
as well as URLs for NNTP newsgroup(s).