From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Jil Rouceau <jilrouceau@gmail.com>
Cc: manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com,
gregkh@linuxfoundation.org, netdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: qlge: qlge_main.c: fixed spaces coding style issues
Date: Mon, 1 Jun 2020 14:19:47 +0900 [thread overview]
Message-ID: <20200601051947.GA12667@f3> (raw)
In-Reply-To: <20200529151749.34018-1-jilrouceau@gmail.com>
On 2020-05-29 17:17 +0200, Jil Rouceau wrote:
> Fixed the missing spaces before and after binary operators.
>
> Signed-off-by: Jil Rouceau <jilrouceau@gmail.com>
This patch does not apply cleanly. I think your base tree is missing
commit ec269f1250c6 ("staging: qlge: Remove unnecessary spaces in
qlge_main.c").
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Jil Rouceau <jilrouceau@gmail.com>
Cc: devel@driverdev.osuosl.org, GR-Linux-NIC-Dev@marvell.com,
manishc@marvell.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] staging: qlge: qlge_main.c: fixed spaces coding style issues
Date: Mon, 1 Jun 2020 14:19:47 +0900 [thread overview]
Message-ID: <20200601051947.GA12667@f3> (raw)
In-Reply-To: <20200529151749.34018-1-jilrouceau@gmail.com>
On 2020-05-29 17:17 +0200, Jil Rouceau wrote:
> Fixed the missing spaces before and after binary operators.
>
> Signed-off-by: Jil Rouceau <jilrouceau@gmail.com>
This patch does not apply cleanly. I think your base tree is missing
commit ec269f1250c6 ("staging: qlge: Remove unnecessary spaces in
qlge_main.c").
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-06-01 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 15:17 [PATCH] staging: qlge: qlge_main.c: fixed spaces coding style issues Jil Rouceau
2020-05-29 15:17 ` Jil Rouceau
2020-06-01 5:19 ` Benjamin Poirier [this message]
2020-06-01 5:19 ` Benjamin Poirier
2020-06-01 10:36 ` Jil Rouceau
2020-06-01 10:36 ` Jil Rouceau
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=20200601051947.GA12667@f3 \
--to=benjamin.poirier@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jilrouceau@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@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.