From: Alan Cox <alan@linux.intel.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] goldfish: framebuffer
Date: Sat, 26 Jan 2013 00:27:45 +0000 [thread overview]
Message-ID: <20130126002745.3eeca45e@bob.linux.org.uk> (raw)
In-Reply-To: <20130125153100.7317.23971.stgit@bob.linux.org.uk>
> hm, it's unclear whether the [] comments apply to the line above or to
> the line below. I converted it to my usual form. I hope I got it
> right!
Below so you got them all one out 8)
Alan
prev parent reply other threads:[~2013-01-26 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 15:31 [PATCH] goldfish: framebuffer Alan Cox
2013-01-25 22:44 ` Andrew Morton
2013-01-26 0:12 ` Andrew Morton
2013-01-26 0:27 ` Alan Cox [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=20130126002745.3eeca45e@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=linux-fbdev@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 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).