All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: New warning
Date: Fri, 22 Jun 2012 07:31:49 -0600	[thread overview]
Message-ID: <4FE473C5.5030601@mlbassoc.com> (raw)
In-Reply-To: <1665284.yNCLAGgIcC@helios>

On 2012-06-22 07:05, Paul Eggleton wrote:
> On Friday 22 June 2012 14:01:39 Paul Eggleton wrote:
>> Rather than ${MACHINE}.patch, the traditional way to do this is to have a
>> generic name for the file and then use a MACHINE-named subdirectory within
>> your BSP layers to define the machine-specific version. You can always make
>> the dummy patch not apply or specifically check for some aspect added by
>> the dummy in do_configure.
>
> (Assuming you use a dummy file that is - with the COMPATIBLE_MACHINE fix I
> suggested this is not necessary; this was from an earlier edit of my message.)

I like the idea of using COMPATIBLE_MACHINE - I think I can make that work well.

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2012-06-22 13:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 19:12 New warning Gary Thomas
2012-06-20 21:55 ` Khem Raj
2012-06-20 22:51   ` Gary Thomas
2012-06-21  8:26     ` Andrea Adami
2012-06-22  9:44     ` Paul Eggleton
2012-06-22 11:49       ` Gary Thomas
2012-06-22 12:35         ` Tomas Frydrych
2012-06-22 13:01         ` Paul Eggleton
2012-06-22 13:05           ` Paul Eggleton
2012-06-22 13:31             ` Gary Thomas [this message]
2012-06-22 14:25         ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2012-10-02 15:34 Gary Thomas
2012-10-02 15:43 ` Richard Purdie
2012-10-03  6:22   ` Khem Raj
2016-06-08  2:55 Gary Thomas
2016-06-08  3:20 ` Christopher Larson

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=4FE473C5.5030601@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.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.