From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v3 1/1] DA8XX/OMAP-L1XX: FB: Implement double buffering
Date: Wed, 07 Apr 2010 21:16:37 +0000 [thread overview]
Message-ID: <876343arpm.fsf@deeprootsystems.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE89445316FACC@dlee02.ent.ti.com>
"Ambrose, Martin" <martin@ti.com> writes:
> On Mon, Apr 05, 2010 at 17:35:38, Kevin Hilman wrote:
>
>> "Ambrose, Martin" <martin@ti.com> writes:
>>
>> > This work includes the following:
>> > . Implement handler for FBIO_WAITFORVSYNC ioctl.
>> >
>> > . Allocate the data and palette buffers separately.
>> > A consequence of this is that the palette and data loading is now
>> > done in different phases. And that the LCD must be disabled
>> > temporarily after the palette is loaded but this will only happen
>> > once after init and each time the palette is changed. I think this
>> > is OK.
>> >
>> > . Allocate two (ping and pong) framebuffers from memory.
>> >
>> > . Add pan_display handler which toggles the LCDC DMA registers between
>> > the ping and pong buffers.
>> >
>> > Signed-off-by: Martin Ambrose <martin@ti.com>
>>
>> Your mailer (probably outlook) is converting all tabs to spaces
>> resulting in a patch that wont apply.
>>
>> I recommend using git-format-patch + git-send-email directly to your
>> SMTP server to avoid outlook mangling.
>
> Sorry about this but I'm floundering. The problem I'm having is that my git-send-email
> is being rejected by several of the recipients on this thread (notably linux-fbdev).
> The reason is that their servers perform sender verification which is fair and understandable.
> See my first attempt at sending the patch which made it to davinci-linux-open-source but
> not fbdev. My attempt at a solution was to first send it to my corporate account, which doesn't
> verify the address, then forward from Outlook. But this is non-functional as you pointed out.
>
> I am not an email expert by any means and don't know how to test different options without
> spamming the mailing lists with test emails. The root cause, I think, is that even though
> I am using git-send-email with the .gitconfig pointing to our corporate mail server the resultant
> header (or maybe ID) is not passing the verification step on the receiving end.
>
> I have tried from both within cygwin and linux running under VMWare. Next step will be
> to try and send from a real linux machine on the corporate network but I'm doubting this
> will resolve the problem. And/or see if I can script Outlook to not convert whitespace --
> this I can test without annoying others.
Not sure what is going wrong, but I know that there are many folks
inside TI who are using git-send-email successfully. Maybe ask
around.
Alternatively, you could use a gmail account as well. See this
GitTips page where it describes how to send using gmail:
https://git.wiki.kernel.org/index.php/GitTips#Mail
Kevin
prev parent reply other threads:[~2010-04-07 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 21:54 [PATCH v3 1/1] DA8XX/OMAP-L1XX: FB: Implement double buffering Ambrose, Martin
2010-04-05 22:35 ` Kevin Hilman
2010-04-07 21:05 ` Ambrose, Martin
2010-04-07 21:16 ` Kevin Hilman [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=876343arpm.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-fbdev@vger.kernel.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.