From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Colin King <colin.king@canonical.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: core: clean up indentation issue
Date: Wed, 25 Sep 2019 11:47:41 +0000 [thread overview]
Message-ID: <20190925114741.GD27389@kadam> (raw)
In-Reply-To: <nycvar.YFH.7.76.1909231303180.1459@cbobk.fhfr.pm>
On Mon, Sep 23, 2019 at 01:04:13PM +0200, Jiri Kosina wrote:
> On Sun, 22 Sep 2019, Colin King wrote:
>
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > There is an if statement that is indented by one extra space,
> > fix this by removing the extraneous space.
> >
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/hid/hid-core.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> > index 3eaee2c37931..9469c382a182 100644
> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -2329,10 +2329,10 @@ int hid_add_device(struct hid_device *hdev)
> > /*
> > * Check for the mandatory transport channel.
> > */
> > - if (!hdev->ll_driver->raw_request) {
> > + if (!hdev->ll_driver->raw_request) {
> > hid_err(hdev, "transport driver missing .raw_request()\n");
> > return -EINVAL;
> > - }
> > + }
>
> Let's not pollute git blame and wait for an ocasion when we need to touch
> the code for some more valid reason.
Just use `git blame -w`.
This probably came from a Smatch warning. Smatch warns very seldom
warns about style issues, but in this case the indenting is legitimately
bad.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Colin King <colin.king@canonical.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: core: clean up indentation issue
Date: Wed, 25 Sep 2019 14:47:41 +0300 [thread overview]
Message-ID: <20190925114741.GD27389@kadam> (raw)
In-Reply-To: <nycvar.YFH.7.76.1909231303180.1459@cbobk.fhfr.pm>
On Mon, Sep 23, 2019 at 01:04:13PM +0200, Jiri Kosina wrote:
> On Sun, 22 Sep 2019, Colin King wrote:
>
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > There is an if statement that is indented by one extra space,
> > fix this by removing the extraneous space.
> >
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/hid/hid-core.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> > index 3eaee2c37931..9469c382a182 100644
> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -2329,10 +2329,10 @@ int hid_add_device(struct hid_device *hdev)
> > /*
> > * Check for the mandatory transport channel.
> > */
> > - if (!hdev->ll_driver->raw_request) {
> > + if (!hdev->ll_driver->raw_request) {
> > hid_err(hdev, "transport driver missing .raw_request()\n");
> > return -EINVAL;
> > - }
> > + }
>
> Let's not pollute git blame and wait for an ocasion when we need to touch
> the code for some more valid reason.
Just use `git blame -w`.
This probably came from a Smatch warning. Smatch warns very seldom
warns about style issues, but in this case the indenting is legitimately
bad.
regards,
dan carpenter
next prev parent reply other threads:[~2019-09-25 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 11:50 [PATCH] HID: core: clean up indentation issue Colin King
2019-09-22 11:50 ` Colin King
2019-09-23 11:04 ` Jiri Kosina
2019-09-23 11:04 ` Jiri Kosina
2019-09-25 11:47 ` Dan Carpenter [this message]
2019-09-25 11:47 ` Dan Carpenter
2019-09-27 10:04 ` Benjamin Tissoires
2019-09-27 10:04 ` Benjamin Tissoires
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=20190925114741.GD27389@kadam \
--to=dan.carpenter@oracle.com \
--cc=benjamin.tissoires@redhat.com \
--cc=colin.king@canonical.com \
--cc=jikos@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--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 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.