From: Derek Robson <robsonde@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: mchehab@kernel.org, gregkh@linuxfoundation.org,
swarren@wwwdotorg.org, lee@kernel.org, eric@anholt.net,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
arnd@arndb.de, mzoran@crowfest.net, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] Staging: media: platform: bcm2835 - Style fix
Date: Sun, 5 Mar 2017 10:43:19 +1300 [thread overview]
Message-ID: <20170304214319.GA15368@bigbird> (raw)
In-Reply-To: <20170304113548.GA4386@mwanda>
On Sat, Mar 04, 2017 at 02:57:22PM +0300, Dan Carpenter wrote:
> Copy a patch prefix that everyone else has been using:
>
> git log --oneline drivers/staging/media/platform/bcm2835/
>
> The subject is too vague as well.
Is this what you are looking for?
[patch] Staging: bcm2835: fixed style of block comments
And should I just re-send as a V2 with new subject?
Thanks
next prev parent reply other threads:[~2017-03-04 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 1:31 [PATCH] Staging: media: platform: bcm2835 - Style fix Derek Robson
2017-03-04 11:57 ` Dan Carpenter
2017-03-04 21:43 ` Derek Robson [this message]
2017-03-06 12:51 ` Greg KH
2017-03-06 15:23 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2017-02-11 1:10 [PATCH] Staging: media: platform: bcm2835 - style fix Derek Robson
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=20170304214319.GA15368@bigbird \
--to=robsonde@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=mzoran@crowfest.net \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.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).