[U-Boot] [PATCH] M28: GPIO pin validity check added

[Robert Deliën]

> sorry if my messages have been a bit harsh with gpio freedback.  the unwrapped 
> lines and broken patch formats make me see red.

I understand; There are rules to adhere to.
But please also understand what I'm working with here. Making a single patch takes me - I kid you not - one hour. And still it comes out borked.

We are obliged to strictly work under Windows. Laptops with full partition true crypt avoids dual boot and gets the i7 quad-core on it's knees like a heroine hooker. On that base I'm running VM-ware...

At the office we're using Perforce. Not a bad system, but it doesn't deal with patches very well and it's inaccessible from my home office. So I'm using Subversion on my NAS as an intermediate archive to work from, committing my changes to P4 every now and then. You guys are using Git; I'm sure it's superior but I don't have time now to figure that one beyond the basics. Every time I need to make or re-make a patch, I have to clone a clean Git repository, revert my SVN workspace back to the work I'm making a patch off, merge that into the clean Git repository and create a new patch.

And I still have to mail the patch. No attachments allowed, I understand, but copying and pasting between a Linux VM and Windows host trashes the leading space, so I either have to go through the patch and put it back myself. Or I can use Exchange web-based mail, that sometimes decides to send HTML mail anyway.

In my home office I'm using a 12-core MacPro as a workstation. Again Linux is under a VM, because I need a Windows VM too, to have crippled access to the office network. To post patches from my home office, I'm using Mac Mail through my own windows server, but Mail somehow doesn't offer the feature to wrap lines at column 72. Instead it uses the format designator to indicate flow-format, understood by any modern email program, but not anticipating people on the other side receiving email in Vim, or applying patches directly from their mailbox.

So even though I had finally convinced management that it's in their best interest to get our work back into the mainline, I decided to bail out because it's just too much work. Even though not ideal, I think we're better off maintaining our 100 lines worth of work. And even if all technical difficulties could be fixed - I'll express myself mildly, but I cannot leave this unsaid - the social standards here are not really my thing.

Robert.