From: Sakari Ailus <sakari.ailus@iki.fi>
To: Philipp Guendisch <philipp.guendisch@fau.de>
Cc: mchehab@kernel.org, gregkh@linuxfoundation.org,
alan@linux.intel.com, jeremy.lefaure@lse.epita.fr,
fabf@skynet.be, rvarsha016@gmail.com, chris.baller@gmx.de,
robsonde@gmail.com, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH 1/2] staging: atomisp2: hmm: Fixed comment style
Date: Tue, 11 Jul 2017 18:27:58 +0300 [thread overview]
Message-ID: <20170711152758.3azqdhfyeiyagtv7@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <1499712981-18363-1-git-send-email-philipp.guendisch@fau.de>
On Mon, Jul 10, 2017 at 08:56:20PM +0200, Philipp Guendisch wrote:
> This patch fixed comment style. Semantic should not be affected.
> There are also two warnings left about too long lines, which
> reduce readability if changed.
>
> Signed-off-by: Philipp Guendisch <philipp.guendisch@fau.de>
> Signed-off-by: Chris Baller <chris.baller@gmx.de>
Hi Philipp,
The patches don't apply. Recently there have been many atomisp patches
being posted and I've applied them to the atomisp branch here:
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=atomisp>
Could you rebase yours on top of that, please?
--
Regards,
Sakari Ailus
e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
next prev parent reply other threads:[~2017-07-11 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 18:56 [PATCH 1/2] staging: atomisp2: hmm: Fixed comment style Philipp Guendisch
2017-07-10 18:56 ` [PATCH 2/2] staging: atomisp2: hmm: Alignment code Philipp Guendisch
2017-07-11 15:27 ` Sakari Ailus [this message]
2017-07-13 6:55 ` [PATCH v2 1/2] staging: atomisp2: hmm: Fixed comment style Philipp Guendisch
2017-07-13 6:55 ` [PATCH v2 2/2] staging: atomisp2: hmm: Alignment code (rebased) Philipp Guendisch
2017-07-13 15:45 ` Sakari Ailus
[not found] ` <43B470FF-66D0-49D5-9944-01799E48805E@fau.de>
2017-07-17 21:31 ` Sakari Ailus
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=20170711152758.3azqdhfyeiyagtv7@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=alan@linux.intel.com \
--cc=chris.baller@gmx.de \
--cc=devel@driverdev.osuosl.org \
--cc=fabf@skynet.be \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=philipp.guendisch@fau.de \
--cc=robsonde@gmail.com \
--cc=rvarsha016@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.