From: Greg KH <gregkh@linuxfoundation.org>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: devel@driverdev.osuosl.org, isdn@linux-pingi.de,
linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [v1] i4l: act2000: act2000:- Do not use 'asm/io.h' directly, use 'linux/io.h'.
Date: Thu, 5 Jan 2017 13:05:23 +0100 [thread overview]
Message-ID: <20170105120523.GA23872@kroah.com> (raw)
In-Reply-To: <54dd4d9a-7561-8c8a-bc36-2e082fe88725@gmail.com>
On Thu, Jan 05, 2017 at 05:25:05PM +0530, Arvind Yadav wrote:
> Please find my comment below.
Where? What happened to your email quoting?
> Thanks
> -Arvind
>
> On Thursday 05 January 2017 05:16 PM, Greg KH wrote:
> > On Thu, Jan 05, 2017 at 04:09:24PM +0530, Arvind Yadav wrote:
> > > Make uniform definition of ioremap, ioremap_wc, ioremap_wt and
> > > ioremap_cache, tree-wide.
> > That doesn't make much sense, and doesn't match the subject: or the
> > patch itself.
> > -- Please refer the commit which is already in main-lined.
> > commit 2584cf83578c26db144730ef498f4070f82ee3ea
Ah, here it is, please quote stuff correctly.
If you are referring to something else, great, then say so in the commit
itself. Every commit should be self-explanatory, how am I supposed to
know this.
And this text still doesn't make sense to me, please fix.
> > And what is with the "[v1]"?
> > ---V1 is stands for patch set version 1
Please read Documentation/SubmittingPatches for how to properly label
patches, don't make new things up, we have too many different developers
(i.e. 4000+) for everyone to do their own unique thing. :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-05 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 10:39 [v1] i4l: act2000: act2000:- Do not use 'asm/io.h' directly, use 'linux/io.h' Arvind Yadav
2017-01-05 11:46 ` Greg KH
2017-01-05 11:55 ` Arvind Yadav
2017-01-05 12:05 ` Greg KH [this message]
2017-01-06 6:20 ` Arvind Yadav
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=20170105120523.GA23872@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=isdn@linux-pingi.de \
--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