From: Breno Leitao <brenohl@br.ibm.com>
To: Zac Storer <zac.3.14159@gmail.com>
Cc: leitao@linux.vnet.ibm.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com>
Subject: Re: [PATCH 29/29] Drivers: tty: serial: jsm: jsm_tty: fixed a brace coding style issue
Date: Fri, 18 Nov 2011 11:30:31 -0300 [thread overview]
Message-ID: <4EC66C07.9020009@br.ibm.com> (raw)
In-Reply-To: <1321596182-11031-1-git-send-email-zac.3.14159@gmail.com>
On 11/18/2011 03:03 AM, Zac Storer wrote:
> Fixed a brace coding style issue.
>
> Signed-off-by: Zac Storer <zac.3.14159@gmail.com>
Acked-by: Breno Leitao <brenohl@br.ibm.com>
next prev parent reply other threads:[~2011-11-18 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 6:03 [PATCH 29/29] Drivers: tty: serial: jsm: jsm_tty: fixed a brace coding style issue Zac Storer
2011-11-18 14:30 ` Breno Leitao [this message]
2012-01-06 18:26 ` Lucas Kannebley Tavares
2012-01-06 19:46 ` Lucas Kannebley Tavares
2012-01-06 19:53 ` Greg KH
2012-01-06 20:08 ` Lucas Kannebley Tavares
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=4EC66C07.9020009@br.ibm.com \
--to=brenohl@br.ibm.com \
--cc=leitao@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lucaskt@linux.vnet.ibm.com \
--cc=zac.3.14159@gmail.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;
as well as URLs for NNTP newsgroup(s).