From: Jiri Slaby <jslaby@suse.cz>
To: unlisted-recipients:; (no To-header on input)
Cc: gregkh@linuxfoundation.org, alan@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] TTY: mn10300-serial, fix build breakage
Date: Wed, 16 Jan 2013 14:50:05 +0100 [thread overview]
Message-ID: <50F6B00D.4060808@suse.cz> (raw)
In-Reply-To: <1358343907-28142-2-git-send-email-jslaby@suse.cz>
On 01/16/2013 02:45 PM, Jiri Slaby wrote:
> I did not notice because I did not even find a compiler for that new
> architecture.
I'm not sure why I thought it's new...
--
js
suse labs
prev parent reply other threads:[~2013-01-16 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:45 [PATCH 1/2] TTY: ip22zilog, fix tty_flip_buffer_push call Jiri Slaby
2013-01-16 13:45 ` [PATCH 2/2] TTY: mn10300-serial, fix build breakage Jiri Slaby
2013-01-16 13:50 ` Jiri Slaby [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=50F6B00D.4060808@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.