From: dan.carpenter@oracle.com (Dan Carpenter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Staging: media: platform: bcm2835 - Style fix
Date: Mon, 6 Mar 2017 18:23:34 +0300 [thread overview]
Message-ID: <20170306152334.GA4335@mwanda> (raw)
In-Reply-To: <20170304214319.GA15368@bigbird>
On Sun, Mar 05, 2017 at 10:43:19AM +1300, Derek Robson wrote:
> 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?
Yes.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Derek Robson <robsonde@gmail.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: Mon, 6 Mar 2017 18:23:34 +0300 [thread overview]
Message-ID: <20170306152334.GA4335@mwanda> (raw)
In-Reply-To: <20170304214319.GA15368@bigbird>
On Sun, Mar 05, 2017 at 10:43:19AM +1300, Derek Robson wrote:
> 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?
Yes.
regards,
dan carpenter
next prev parent reply other threads:[~2017-03-06 15:23 UTC|newest]
Thread overview: 12+ 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 1:31 ` Derek Robson
2017-03-04 11:57 ` Dan Carpenter
2017-03-04 11:57 ` Dan Carpenter
2017-03-04 21:43 ` Derek Robson
2017-03-04 21:43 ` Derek Robson
2017-03-06 12:51 ` Greg KH
2017-03-06 12:51 ` Greg KH
2017-03-06 15:23 ` Dan Carpenter [this message]
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
2017-02-11 1:10 ` 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=20170306152334.GA4335@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.