From: roman.sommer@fau.de
To: "Johan Hovold" <johan@kernel.org>
Cc: "Roman Sommer" <roman.sommer@fau.de>,
linux-kernel@i4.cs.fau.de, "Rui Miguel Silva" <rmfrfs@gmail.com>,
"Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
"Christian Bewermeyer" <christian.bewermeyer@fau.de>
Subject: Re: [PATCH v2] greybus: checkpatch: Change parameter type unsigned to unsigned int
Date: Wed, 11 Jan 2017 15:44:53 +0100 [thread overview]
Message-ID: <cbda8f22165283fe0944bff5f78d31d9.squirrel@faumail.uni-erlangen.de> (raw)
In-Reply-To: <20170111135214.GA7420@localhost>
> You forgot to fix the Subject prefix ("staging: greybus: <summary>").
>
> Care to fix that up and resend?
>
> Thanks,
> Johan
>
As I added the fix for loopback.c, I did not include the "gpio" prefix.
This is what I thought was correct after reading your last mail.
Apparently I misunderstood.
What should the prefix be in this case?
Thanks,
Roman
next prev parent reply other threads:[~2017-01-11 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 16:21 [PATCH] greybus: checkpatch: Change parameter type unsigned to unsigned int Roman Sommer
2017-01-10 16:40 ` Johan Hovold
2017-01-10 17:01 ` roman.sommer
2017-01-11 13:48 ` [PATCH v2] " Roman Sommer
2017-01-11 13:52 ` Johan Hovold
2017-01-11 14:44 ` roman.sommer [this message]
2017-01-11 14:47 ` roman.sommer
2017-01-11 15:00 ` [PATCH v3] staging: " Roman Sommer
2017-01-11 15:08 ` Johan Hovold
2017-01-12 4:50 ` [greybus-dev] " Viresh Kumar
2017-01-12 7:05 ` Dan Carpenter
2017-01-12 8:47 ` Johan Hovold
2017-01-13 20:54 ` [PATCH] staging: greybus: fix checkpatch unsigned warnings Roman Sommer
2017-01-16 9:50 ` Johan Hovold
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=cbda8f22165283fe0944bff5f78d31d9.squirrel@faumail.uni-erlangen.de \
--to=roman.sommer@fau.de \
--cc=christian.bewermeyer@fau.de \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmfrfs@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;
as well as URLs for NNTP newsgroup(s).