From: Hans Verkuil <hverkuil@xs4all.nl>
To: Quytelda Kahja <quytelda@tamalin.org>,
gregkh@linuxfoundation.org, dan.carpenter@oracle.com,
hans.verkuil@cisco.com
Cc: linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Staging: bcm2048: Fix function argument alignment in radio-bcm2048.c.
Date: Mon, 26 Feb 2018 14:51:20 +0100 [thread overview]
Message-ID: <cb62e915-eb9c-9252-1f0a-cc85c8ea3530@xs4all.nl> (raw)
In-Reply-To: <20180220065304.8943-1-quytelda@tamalin.org>
On 02/20/2018 07:53 AM, Quytelda Kahja wrote:
> Fix a coding style problem.
What coding style problem? You should give a short description of
what you are fixing.
>
> Signed-off-by: Quytelda Kahja <quytelda@tamalin.org>
> ---
> This is the patch without the unnecessary fixes for line length.
>
> drivers/staging/media/bcm2048/radio-bcm2048.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/staging/media/bcm2048/radio-bcm2048.c b/drivers/staging/media/bcm2048/radio-bcm2048.c
> index 06d1920150da..f38a4f2acdde 100644
> --- a/drivers/staging/media/bcm2048/radio-bcm2048.c
> +++ b/drivers/staging/media/bcm2048/radio-bcm2048.c
> @@ -1864,7 +1864,7 @@ static int bcm2048_probe(struct bcm2048_device *bdev)
> goto unlock;
>
> err = bcm2048_set_fm_search_rssi_threshold(bdev,
> - BCM2048_DEFAULT_RSSI_THRESHOLD);
> + BCM2048_DEFAULT_RSSI_THRESHOLD);
> if (err < 0)
> goto unlock;
>
Just drop this change: it will replace one warning (non-aligned) with
another (> 80 cols).
This code is fine as it is.
Regards,
Hans
> @@ -1942,9 +1942,9 @@ static irqreturn_t bcm2048_handler(int irq, void *dev)
> */
> #define property_write(prop, type, mask, check) \
> static ssize_t bcm2048_##prop##_write(struct device *dev, \
> - struct device_attribute *attr, \
> - const char *buf, \
> - size_t count) \
> + struct device_attribute *attr, \
> + const char *buf, \
> + size_t count) \
> { \
> struct bcm2048_device *bdev = dev_get_drvdata(dev); \
> type value; \
> @@ -1966,8 +1966,8 @@ static ssize_t bcm2048_##prop##_write(struct device *dev, \
>
> #define property_read(prop, mask) \
> static ssize_t bcm2048_##prop##_read(struct device *dev, \
> - struct device_attribute *attr, \
> - char *buf) \
> + struct device_attribute *attr, \
> + char *buf) \
> { \
> struct bcm2048_device *bdev = dev_get_drvdata(dev); \
> int value; \
> @@ -1985,8 +1985,8 @@ static ssize_t bcm2048_##prop##_read(struct device *dev, \
>
> #define property_signed_read(prop, size, mask) \
> static ssize_t bcm2048_##prop##_read(struct device *dev, \
> - struct device_attribute *attr, \
> - char *buf) \
> + struct device_attribute *attr, \
> + char *buf) \
> { \
> struct bcm2048_device *bdev = dev_get_drvdata(dev); \
> size value; \
> @@ -2005,8 +2005,8 @@ property_read(prop, mask) \
>
> #define property_str_read(prop, size) \
> static ssize_t bcm2048_##prop##_read(struct device *dev, \
> - struct device_attribute *attr, \
> - char *buf) \
> + struct device_attribute *attr, \
> + char *buf) \
> { \
> struct bcm2048_device *bdev = dev_get_drvdata(dev); \
> int count; \
> @@ -2175,7 +2175,7 @@ static int bcm2048_fops_release(struct file *file)
> }
>
> static __poll_t bcm2048_fops_poll(struct file *file,
> - struct poll_table_struct *pts)
> + struct poll_table_struct *pts)
> {
> struct bcm2048_device *bdev = video_drvdata(file);
> __poll_t retval = 0;
>
next prev parent reply other threads:[~2018-02-26 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180219072550.hz4vpomsaz2ajrnm@mwanda>
2018-02-20 6:53 ` [PATCH v2] Staging: bcm2048: Fix function argument alignment in radio-bcm2048.c Quytelda Kahja
2018-02-26 13:51 ` Hans Verkuil [this message]
2018-02-27 1:53 ` Quytelda Kahja
2018-02-27 7:32 ` Hans Verkuil
2018-02-27 13:42 ` Greg KH
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=cb62e915-eb9c-9252-1f0a-cc85c8ea3530@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=quytelda@tamalin.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;
as well as URLs for NNTP newsgroup(s).