linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saiyam Doshi <saiyamdoshi.in@gmail.com>
To: Wolfram Sang <wsa@the-dreams.de>, Markus.Elfring@web.de
Cc: Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [v2 0/3] Fix issues reported by Coccinelle
Date: Sun, 22 Sep 2019 22:39:06 +0530	[thread overview]
Message-ID: <20190922170906.GB5589@SD> (raw)
In-Reply-To: <20190917181423.GB28182@ninjato>

On Tue, Sep 17, 2019 at 08:14:23PM +0200, Wolfram Sang wrote:
> On Tue, Sep 17, 2019 at 08:10:45PM +0200, Markus Elfring wrote:
> > > Using cocciecheck to ensure there are no semantic issues in
> > > i2c-qup driver.
> > 
> > * This wording contains a typo.
> 
> Doesn't matter to me for a cover letter as long as we can understand it.
> 
> > * I would prefer to refer to a desired reduction of a few
> >   source code quality concerns.
> 
> Not needed. I understand what is going on here.

Markus - By "ensure", I mean there are no further cocciecheck issues at this
point in time. And further, what changed is covered in individual patch
changelog. So, I think this information is fine in cover.

> > Can such a prefix be omitted?
Can be, but I like to keep it.

Thanks for review.

-Saiyam

      parent reply	other threads:[~2019-09-22 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 17:27 [PATCH v2 0/3] Fix issues reported by Coccinelle Saiyam Doshi
2019-09-17 18:10 ` [v2 " Markus Elfring
2019-09-17 18:14   ` Wolfram Sang
2019-09-17 18:22     ` Markus Elfring
2019-09-22 17:09     ` Saiyam Doshi [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=20190922170906.GB5589@SD \
    --to=saiyamdoshi.in@gmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=agross@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).