[PATCH] staging: rtl8723au: Fix brace coding style issues reported by checkpatch

[Scott Lovenberg]

On Wed, Oct 29, 2014 at 1:48 AM, Sudip Mukherjee
<sudipm.mukherjee at gmail.com> wrote:
> On Wed, Oct 29, 2014 at 11:38 AM, Scott Lovenberg
> <scott.lovenberg at gmail.com> wrote:
>> On Wed, Oct 29, 2014 at 12:05 AM, Sudip Mukherjee
>> <sudipm.mukherjee at gmail.com> wrote:
>>>
>>> On Wed, Oct 29, 2014 at 7:31 AM, nick <xerofoify at gmail.com> wrote:
>>> > Greg,
>>> > That's fine, I was wondering how long Greg KH takes to get around to picking this up as he is very busy with
>>> > other kernel work.
>>>
>>> it might take a long long time. i think he is very busy now. I have
>>> not seen his replies to patches in the kernel list for atleast last 3
>>> weeks.
>>>
>> [snip]
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>>
>> Nah.  Greg KH is a robot.  I'm firmly convinced that man doesn't
>> sleep.  If I didn't know better, I'd think he's a Cylon.
> well said.
>
>> On a serious note; realistically, a two week window isn't unheard of
>> for getting your patches to mainline.  So long as you're not trying to
>
> mine is three weeks going on now. somehow i have managed to send my
> patches just at the beginning of the merge window.  :(
> yesterday i saw Greg K-H releasing the stable patches , so i guess now
> he will be seeing the pending staging patches.

It also depends on how many hops you are to the maintainer and how
heavy their workload is.  Sometimes you can directly submit to them,
other times your patches will be passed through three trees before
they see mainline.  It all depends on what you're working on and who's
in your "circle".

-- 
Peace and Blessings,
-Scott.