[U-Boot] [PATCH] arm: io.h: replace writeb from macro to inline func

[馬克泡]

Hi Marek,

2011/10/25 Marek Vasut <marek.vasut at gmail.com>:
>> Hi Marek,
>>
[snip]
>> > Anyway, make a gmail account and you should be fine, no ?
>>
>> Except trying to post patches using the gmail web interface is impossible
>> (it converts tabs to spaces for starters)
>
> Well ...
>>
>> And I would not be surprised if Macpual's company firewall blocked outgoing
>> SMTP connections
>
> Ah that's true ... then there's also the possibility to run httunnel and push
> through the firewall that way ;-D

Unfortunately it is also still problem to me.

Actually, I have 2 e-mail account to contribute the u-boot project.

The first one is the one I'm using which let me send patches via Linux
server with git send-email.
However, the mail will be relayed to company's mail server, then the
receiver's e-mail will be checked via e-mail firewall.
The mail will only be forwarded when all the e-mail addresses in the
mail are on the white list.
To add each individual email domain or email account to the white
list, a report and a application is necessary to security department
and need to be signed by CTO.

The second e-mail account will be activate on 2012, which is dedicated
for u-boot project.
It should not have the black/white list problem.
However, every mail send by this account will be CC-ed to managers and CTO.
(Yes, the CTO will read each patch and ask why a patch has been reject
or why the code must be rewritten).
They're afraid of to send out the driver will reveal the hardware
design then other people will copy the hardware design.
And the CTO will ask me why do you need to fix code for another companies,
this should not be a part of my task. @_ at . (Although I'm glad to help on it.)

There is no outgoing SSH tunnel allowed in this company.
However, I'm the only person who have a CTO proved SSH tunnel to push
code into u-boot git.

Although I could set up SSH tunnel and to send patch via another
server outside of my company. They still probably sue me if I don't
use company's email address to contribute the code to public domain.
Hence I can only use gmail to reply but couldn't to send the patches.

Sorry for telling a lot of the mess.
I've forgot there is a restrict to add most of custodians on CC list
when sending patches and picked that task. :(

-- 
Best regards,
Macpaul Lin