Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] linux-yocto/3.10: fix qemuarm boot and spurious mips build warning
Date: Tue, 05 Nov 2013 20:56:17 +0000	[thread overview]
Message-ID: <1383684977.8901.133.camel@x121e.pbcl.net> (raw)
In-Reply-To: <cover.1383677174.git.bruce.ashfield@windriver.com>

On Tue, 2013-11-05 at 13:47 -0500, Bruce Ashfield wrote:
> I don't have anything extra to add outside of what I put in the
> patch commit log ..

That's certainly a good thing and to be applauded, but in this situation
maybe you could consider just sending the patch without a cover letter.

p.




  parent reply	other threads:[~2013-11-05 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 18:47 [PATCH 0/1] linux-yocto/3.10: fix qemuarm boot and spurious mips build warning Bruce Ashfield
2013-11-05 18:47 ` [PATCH 1/1] " Bruce Ashfield
2013-11-05 20:56 ` Phil Blundell [this message]
2013-11-06  3:21   ` [PATCH 0/1] " Bruce Ashfield
2013-11-07 18:39     ` Darren Hart

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=1383684977.8901.133.camel@x121e.pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.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