From: Greg KH <gregkh@linuxfoundation.org>
To: Robert Nachlinger <robert.nachlinger@googlemail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: gdm724x: fix space before comma coding style issue in gdm_mux.c
Date: Sat, 17 Jan 2015 14:57:11 -0800 [thread overview]
Message-ID: <20150117225711.GA30146@kroah.com> (raw)
In-Reply-To: <1419158683-6113-1-git-send-email-robert.nachlinger@googlemail.com>
On Sun, Dec 21, 2014 at 11:44:43AM +0100, Robert Nachlinger wrote:
> This is a patch to the gdm_mux.c file that fixes a space before comma
> coding style issue found by the checkpatch.pl tool.
>
> Signed-off-by: Robert Nachlinger <robert.nachlinger@googlemail.com>
> ---
> drivers/staging/gdm724x/gdm_mux.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/gdm724x/gdm_mux.c b/drivers/staging/gdm724x/gdm_mux.c
> index b5b063a..d1ab996 100644
> --- a/drivers/staging/gdm724x/gdm_mux.c
> +++ b/drivers/staging/gdm724x/gdm_mux.c
> @@ -220,7 +220,7 @@ static int up_to_host(struct mux_rx *r)
> static void do_rx(struct work_struct *work)
> {
> struct mux_dev *mux_dev =
> - container_of(work, struct mux_dev , work_rx.work);
> + container_of(work, struct mux_dev, work_rx.work);
> struct mux_rx *r;
> struct rx_cxt *rx = (struct rx_cxt *)&mux_dev->rx;
> unsigned long flags;
> --
> 2.2.0
Someone else sent this same patch :(
next prev parent reply other threads:[~2015-01-17 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 10:44 [PATCH] Staging: gdm724x: fix space before comma coding style issue in gdm_mux.c Robert Nachlinger
2015-01-17 22:57 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-18 16:57 Robert Nachlinger
2014-12-18 16:46 Robert Nachlinger
2014-12-18 16:52 ` Greg KH
2014-12-19 22:58 ` Greg KH
[not found] ` <CABdSh179apawgBKm9=2vBaxVBPTemz4SPhDcgf_2kwk7rsn2oA@mail.gmail.com>
2014-12-20 17:12 ` Greg KH
2014-12-18 14:09 Robert Nachlinger
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=20150117225711.GA30146@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.nachlinger@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox