From: Greg KH <gregkh@linuxfoundation.org>
To: Ran Algawi <ran.algawi@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [Patch] Staging: media: bcm2048: fixed errors and warnings
Date: Fri, 10 Feb 2017 15:00:45 +0100 [thread overview]
Message-ID: <20170210140045.GA28966@kroah.com> (raw)
In-Reply-To: <20170210094141.GA24612@LestatChateau>
On Fri, Feb 10, 2017 at 11:41:41AM +0200, Ran Algawi wrote:
>
<snip>
Never attach patches, and always test-build them yourself to ensure they
do not break the build :(
greg k-h
prev parent reply other threads:[~2017-02-10 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 9:41 [Patch] Staging: media: bcm2048: fixed errors and warnings Ran Algawi
2017-02-10 11:39 ` kbuild test robot
2017-02-10 14:00 ` Greg KH [this message]
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=20170210140045.GA28966@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ran.algawi@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 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.