From: Ismael Luceno <ismael.luceno@gmail.com>
To: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Andrey Utkin <andrey_utkin@fastmail.com>,
Ismael Luceno <ismael@iodev.co.uk>,
Linux Media <linux-media@vger.kernel.org>,
Curtis Hall <chall@corp.bluecherry.net>,
Bluecherry Maintainers <maintainers@bluecherrydvr.com>
Subject: Re: [PATCH 1/2] solo6x10: Set FRAME_BUF_SIZE to 200KB
Date: Wed, 4 May 2016 12:09:28 -0300 [thread overview]
Message-ID: <20160504150928.GD9208@pirotess.lan> (raw)
In-Reply-To: <CAM_ZknWELGNLnwFR66WbSEtDRHE2cEnkSOAOjAtd=aRXBgqgxw@mail.gmail.com>
On 04/May/2016 17:22, Andrey Utkin wrote:
> On Wed, May 4, 2016 at 5:04 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> > BTW, looking at the MAINTAINERS file I see two email addresses for Andrey,
> > neither of which is the fastmail.com address this email came from.
>
> Now I'm replying from corporate email.
>
> > Andrey, it might be a good idea to post such fixes to the mailinglist sooner,
> > both to prevent situations like this and to keep the diffs between mainline
> > and your internal code as small as possible.
>
> In a word - we would do what is possible to achieve that, but
> there's little time and little incentive for that.
> The codebases have already diverged a lot, having unique sets of runtime bugs.
The divergence is due to the vb2 porting effort by Hans. History
was not properly conserved, but it is otherwise compatible, and most
changes can still be ported back and forth without trouble.
> And this exact issue alone is not resolved yet in a good way and is
> not actually critical.
> Merging would require a lot of working time. And it is complicated by
> the fact that there's not going to be any new manufacturing orders
> (the minimal order quantity is too high for Bluecherry), and that
> we have picked tw5864 as reachable for retail orders.
Right now it would be easy to keep the two in sync, there has been
not many changes since I left, and if changes are integrated into
mainline first, there will be no further issues.
next prev parent reply other threads:[~2016-05-04 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 3:17 [PATCH 1/2] solo6x10: Set FRAME_BUF_SIZE to 200KB Ismael Luceno
2016-04-30 3:17 ` [PATCH 2/2] solo6x10: Simplify solo_enum_ext_input Ismael Luceno
2016-05-04 8:02 ` Hans Verkuil
2016-05-04 11:42 ` Ismael Luceno
2016-05-04 11:50 ` Hans Verkuil
2016-05-04 13:34 ` [PATCH 1/2] solo6x10: Set FRAME_BUF_SIZE to 200KB Andrey Utkin
2016-05-04 14:04 ` Hans Verkuil
2016-05-04 14:22 ` Andrey Utkin
2016-05-04 15:09 ` Ismael Luceno [this message]
2016-05-04 15:41 ` Hans Verkuil
2016-05-04 14:53 ` Ismael Luceno
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=20160504150928.GD9208@pirotess.lan \
--to=ismael.luceno@gmail.com \
--cc=andrey.utkin@corp.bluecherry.net \
--cc=andrey_utkin@fastmail.com \
--cc=chall@corp.bluecherry.net \
--cc=hverkuil@xs4all.nl \
--cc=ismael@iodev.co.uk \
--cc=linux-media@vger.kernel.org \
--cc=maintainers@bluecherrydvr.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