From: Greg KH <greg@kroah.com>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
jirislaby@gmail.com, linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: mxser: Fix build warning introduced by dfc7b837c7f9 (Re: linux-next: build warning after merge of the tty.current tree)
Date: Wed, 22 May 2013 08:35:30 -0700 [thread overview]
Message-ID: <20130522153530.GC10402@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1305221109110.10829@lnfm1.sai.msu.ru>
On Wed, May 22, 2013 at 11:13:38AM +0400, Matwey V. Kornilov wrote:
> From: Matwey V. Kornilov <matwey@sai.msu.ru>
>
> Fix build warning at mxser.c introduced by dfc7b837c7f9
>
> Signed-off-by: Matwey V. Kornilov <matwey@sai.msu.ru>
> ---
You forgot to add "reported-by:" :(
I'll go do it by hand...
thanks,
greg k-h
prev parent reply other threads:[~2013-05-22 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 3:37 linux-next: build warning after merge of the tty.current tree Stephen Rothwell
2013-05-22 7:13 ` [PATCH] tty: mxser: Fix build warning introduced by dfc7b837c7f9 (Re: linux-next: build warning after merge of the tty.current tree) Matwey V. Kornilov
2013-05-22 15:35 ` Greg KH [this message]
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=20130522153530.GC10402@kroah.com \
--to=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--cc=sfr@canb.auug.org.au \
/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