From: Greg KH <gregkh@linuxfoundation.org>
To: Chetan Sethi <cpsethi369@gmail.com>
Cc: devel@driverdev.osuosl.org, punitvara@gmail.com,
wsa@the-dreams.de, mattkilgore12@gmail.com,
linux-kernel@vger.kernel.org, weiyongjun1@huawei.com,
shiva@exdev.nl, bhumirks@gmail.com
Subject: Re: [PATCH v3 4/6] drivers: staging: fix coding style issue of using pr_notice instead of printk
Date: Fri, 24 Feb 2017 18:47:12 +0100 [thread overview]
Message-ID: <20170224174712.GA3217@kroah.com> (raw)
In-Reply-To: <1487324926-29178-1-git-send-email-cpsethi369@gmail.com>
On Fri, Feb 17, 2017 at 06:48:46PM +0900, Chetan Sethi wrote:
> This is 04th patch to ks_wlan.h fixing coding style issue of using
> pr_notice instead of printk, warning as issued by checkpatch.pl
>
> Signed-off-by: Chetan Sethi <cpsethi369@gmail.com>
> ---
> v2:
> - split multiple changes across different patches
> v3:
> - mentioned patch revision in subject
Does not apply to my tree, did I miss some previous patches? Please
resend the whole series.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-24 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170216182800.GA30761@kroah.com>
2017-02-17 9:46 ` [PATCH v3 1/6] staging: ks7010: fixed warning of avoiding line over 80 characters Chetan Sethi
2017-02-17 9:47 ` [PATCH v3 2/6] staging: ks7010: fix coding style issue of enclosing complex macro value in parentheses Chetan Sethi
2017-02-24 17:07 ` Greg KH
2017-02-17 9:48 ` [PATCH v3 3/6] staging: ks7010: fix coding style issue of using tabs instead of spaces Chetan Sethi
2017-02-17 9:48 ` [PATCH v3 4/6] drivers: staging: fix coding style issue of using pr_notice instead of printk Chetan Sethi
2017-02-24 17:47 ` Greg KH [this message]
2017-02-17 9:49 ` [PATCH v3 5/6] drivers: staging: fix coding style issue of using __func__ instead of __FUNCTION__ Chetan Sethi
2017-02-17 9:49 ` [PATCH v3 6/6] drivers: staging: fix coding style issue of aligning comments properly Chetan Sethi
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=20170224174712.GA3217@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhumirks@gmail.com \
--cc=cpsethi369@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattkilgore12@gmail.com \
--cc=punitvara@gmail.com \
--cc=shiva@exdev.nl \
--cc=weiyongjun1@huawei.com \
--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