From: Greg KH <greg@kroah.com>
To: Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com>
Cc: Breno Leitao <brenohl@br.ibm.com>,
Zac Storer <zac.3.14159@gmail.com>,
leitao@linux.vnet.ibm.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 29/29] Drivers: tty: serial: jsm: jsm_tty: fixed a brace coding style issue
Date: Fri, 6 Jan 2012 11:53:32 -0800 [thread overview]
Message-ID: <20120106195332.GA10814@kroah.com> (raw)
In-Reply-To: <4F074F89.6060300@linux.vnet.ibm.com>
On Fri, Jan 06, 2012 at 05:46:17PM -0200, Lucas Kannebley Tavares wrote:
> On 01/06/2012 04:26 PM, Lucas Kannebley Tavares wrote:
> >On 11/18/2011 12:30 PM, Breno Leitao wrote:
> >>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>
> >Acked-by: Lucas Kannebley Tavares<lucaskt@linux.vnet.ibm.com>
> >
>
> Adding Alan and Greg so they can catch this up on their trees.
Catch what up with what?
What patch is this? Where is it? Why wasn't it sent to me in the first
place?
Also note, the merge window for new patches to be sent to subsystem
maintainers has been over for a week or so now, all of of the
maintainers are now busy merging stuff with Linus, so trivial stuff like
this is going to have to wait a few weeks at the earliest before it can
start to be queued up.
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-06 19:53 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
2012-01-06 18:26 ` Lucas Kannebley Tavares
2012-01-06 19:46 ` Lucas Kannebley Tavares
2012-01-06 19:53 ` Greg KH [this message]
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=20120106195332.GA10814@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=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