From: Greg KH <gregkh@linuxfoundation.org>
To: "JoonHwan.Kim" <spilit464@gmail.com>
Cc: alan@linux.intel.com, sakari.ailus@linux.intel.com,
mchehab@kernel.org, devel@driverdev.osuosl.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] media: staging: atomisp: add a blank line after declarations
Date: Sat, 16 Jun 2018 07:03:01 +0000 [thread overview]
Message-ID: <20180616070301.GA30558@kroah.com> (raw)
In-Reply-To: <2750553.3y1WJKmnP5@joonhwan-virtualbox>
On Sat, Jun 16, 2018 at 01:30:48PM +0900, JoonHwan.Kim wrote:
> fix checkpatch.pl warning:
> * Missing a blank line after declarations
>
> Signed-off-by: Joonhwan Kim <spilit464@gmail.com>
> ---
> drivers/staging/media/atomisp/pci/atomisp2/atomisp_ioctl.c | 5 +++++
Always work against the latest development tree so you do not duplicate
work. This file is gone in Linus's tree, and in linux-next :(
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: "JoonHwan.Kim" <spilit464@gmail.com>
Cc: alan@linux.intel.com, sakari.ailus@linux.intel.com,
mchehab@kernel.org, devel@driverdev.osuosl.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
andriy.shevchenko@linux.intel.com, linux-media@vger.kernel.org
Subject: Re: [PATCH] media: staging: atomisp: add a blank line after declarations
Date: Sat, 16 Jun 2018 09:03:01 +0200 [thread overview]
Message-ID: <20180616070301.GA30558@kroah.com> (raw)
In-Reply-To: <2750553.3y1WJKmnP5@joonhwan-virtualbox>
On Sat, Jun 16, 2018 at 01:30:48PM +0900, JoonHwan.Kim wrote:
> fix checkpatch.pl warning:
> * Missing a blank line after declarations
>
> Signed-off-by: Joonhwan Kim <spilit464@gmail.com>
> ---
> drivers/staging/media/atomisp/pci/atomisp2/atomisp_ioctl.c | 5 +++++
Always work against the latest development tree so you do not duplicate
work. This file is gone in Linus's tree, and in linux-next :(
thanks,
greg k-h
next prev parent reply other threads:[~2018-06-16 7:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 4:30 [PATCH] media: staging: atomisp: add a blank line after declarations JoonHwan.Kim
2018-06-16 4:30 ` JoonHwan.Kim
2018-06-16 7:03 ` Greg KH [this message]
2018-06-16 7:03 ` Greg KH
2018-06-16 9:06 ` Dan Carpenter
2018-06-16 9:06 ` Dan Carpenter
2018-06-16 10:20 ` 김준환
2018-06-16 10:20 ` 김준환
2018-06-16 12:46 ` Dan Carpenter
2018-06-16 12:46 ` Dan Carpenter
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=20180616070301.GA30558@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=spilit464@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.