From: Joe Perches <joe@perches.com>
To: "Bjørn Mork" <bjorn@mork.no>, "Greg KH" <gregkh@linuxfoundation.org>
Cc: Martin Karamihov <martinowar@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Larry.Finger@lwfinger.net
Subject: Re: [PATCH] staging: rtl8188eu: checkpatch fixes: removed not necessary braces {}
Date: Thu, 02 Feb 2017 14:53:52 -0800 [thread overview]
Message-ID: <1486076032.22276.45.camel@perches.com> (raw)
In-Reply-To: <87r33lg6ku.fsf@miraculix.mork.no>
On Sun, 2017-01-29 at 17:43 +0100, Bjørn Mork wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> > Please take some time, and go read Documentation/SubmittingPatches.
>
> That's quickly done nowadays:
>
> bjorn@miraculix:/usr/local/src/git/linux$ cat Documentation/SubmittingPatches
> This file has moved to process/submitting-patches.rst
>
>
> I don't know why it was necessary to move that file, but it looks like
> you, and the gazillion links and references to this document, just have
> to adopt to a new location.
>
> Or submit a patch to fix it :)
I did exactly that.
https://lkml.org/lkml/2017/1/10/1059
next prev parent reply other threads:[~2017-02-02 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 8:49 [PATCH] staging: rtl8188eu: checkpatch fixes: removed not necessary braces {} Martin Karamihov
2017-01-28 9:11 ` Greg KH
2017-01-29 16:43 ` Bjørn Mork
2017-01-29 18:57 ` martinowar
2017-02-02 22:53 ` Joe Perches [this message]
2017-01-31 19:24 ` [PATCH v2] staging: rtl8188eu: remove not necessary braces {} (checkpatch fix) Martin Karamihov
2017-01-31 22:39 ` Joe Perches
2017-02-01 16:36 ` Martin Karamihov
2017-02-01 18:11 ` Joe Perches
2017-02-02 6:06 ` Martin Karamihov
2017-02-02 23:32 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2017-01-28 8:34 [PATCH] staging: rtl8188eu: checkpatch fixes: removed not necessary braces Martin Karamihov
2017-01-28 8:34 ` [PATCH] staging: rtl8188eu: checkpatch fixes: removed not necessary braces {} Martin Karamihov
2017-01-28 8:41 ` 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=1486076032.22276.45.camel@perches.com \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bjorn@mork.no \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martinowar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox