From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 14/17] infiniband: pa_vnic_encap.h: get rid of a warning
Date: Fri, 27 Mar 2020 12:51:38 -0300 [thread overview]
Message-ID: <20200327155138.GX20941@ziepe.ca> (raw)
In-Reply-To: <20200327153226.1fed1835@coco.lan>
On Fri, Mar 27, 2020 at 03:32:26PM +0100, Mauro Carvalho Chehab wrote:
> Em Wed, 18 Mar 2020 21:36:45 -0300
> Jason Gunthorpe <jgg@ziepe.ca> escreveu:
>
> > On Tue, Mar 17, 2020 at 03:54:23PM +0100, Mauro Carvalho Chehab wrote:
> > > The right markup for a variable is @foo, and not @foo[].
> > >
> > > Using a wrong markup caused this warning:
> > >
> > > ./drivers/infiniband/ulp/opa_vnic/opa_vnic_encap.h:243: WARNING: Inline strong start-string without end-string.
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > > drivers/infiniband/ulp/opa_vnic/opa_vnic_encap.h | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Do you want this to go to the RDMA tree? I wasn't cc'd on the cover
> > letter
>
> Sorry for not answering earlier. Got sidetracked with other things.
>
> Yeah, if there are still time, feel free to pick it. Otherwise,
> I'll likely send again after the merge window, to be applied either
> by you or via the docs tree.
Sure, done
Thanks,
Jason
prev parent reply other threads:[~2020-03-27 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1584456635.git.mchehab+huawei@kernel.org>
2020-03-17 14:54 ` [PATCH 14/17] infiniband: pa_vnic_encap.h: get rid of a warning Mauro Carvalho Chehab
2020-03-19 0:36 ` Jason Gunthorpe
2020-03-27 14:32 ` Mauro Carvalho Chehab
2020-03-27 15:51 ` Jason Gunthorpe [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=20200327155138.GX20941@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=corbet@lwn.net \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=niranjana.vishwanathapura@intel.com \
/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).