From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH 1/2] pinctrl: sh-pfc: fix overly long lines
Date: Mon, 4 Jul 2016 22:20:41 +0300 [thread overview]
Message-ID: <ca47c1a9-a77b-2180-b6e4-a0425a5985a0@cogentembedded.com> (raw)
In-Reply-To: <37b292fe-3a14-62d6-bdc5-7f7e5e93d958@cogentembedded.com>
On 07/04/2016 10:15 PM, Sergei Shtylyov wrote:
>>> The PORT_GP_CFG_<n>() macros take up more than 80 columns -- and not for
>>> a good reason. Make the header file checkpatch.pl-proof at least in this
>>> respect...
>>>
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>
>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>
>> But it doesn't apply, due to "pinctrl: sh-pfc: Initial R8A7796 PFC support"
>
> ... and *still* not merged? Or am I looking at a wrong tree? :-/
>
>> which was submitted one day earlier.
>
> I don't think that matters... What matters are the order of merges.
Moreover, I couldn't find this patch in my mail and in the mail archive
(marc.info) too -- I'm only seeing your comments to that patch. Where can I
find the patch itself?
MBR, Sergei
next prev parent reply other threads:[~2016-07-04 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 21:19 [PATCH 0/2] Add Renesas R8A7792 PFC support Sergei Shtylyov
2016-06-29 21:20 ` [PATCH 1/2] pinctrl: sh-pfc: fix overly long lines Sergei Shtylyov
2016-07-01 7:50 ` Geert Uytterhoeven
2016-07-04 19:15 ` Sergei Shtylyov
2016-07-04 19:18 ` Geert Uytterhoeven
2016-07-04 19:20 ` Sergei Shtylyov [this message]
2016-06-29 21:21 ` [PATCH 2/2] pinctrl: sh-pfc: add R8A7792 PFC support Sergei Shtylyov
2016-07-01 8:04 ` Geert Uytterhoeven
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=ca47c1a9-a77b-2180-b6e4-a0425a5985a0@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@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 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).