Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 5/6] linux-2.6.36: remove ts72xx support because	2.6.38 is now default
Date: Sat, 2 Apr 2011 18:31:01 +0200	[thread overview]
Message-ID: <20110402163101.GA23489@ibawizard.net> (raw)
In-Reply-To: <in7hmh$og5$1@dough.gmane.org>

Koen Kooi <koen@dominion.thruhere.net> [2011-04-02 18:08:48]:

> Is it really necessary to remove it from .36 instead of DP+1;ing .38?

It's not, but wouldn't it be better to remove the patches from the unsupported
kernel version? It's just a start, RFC and if it's ok I would like to remove
the references of ts72xx in all older and unsupported kernel versions. What's
a point of keeping them in oe-dev branch, anyway?

-- ynezz



  reply	other threads:[~2011-04-02 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 14:18 [PATCH 0/6] RFC: patches I plan to push Petr Štetiar
2011-04-02 14:18 ` [PATCH 1/6] zeromq: add new recipe for version 2.1.1 Petr Štetiar
2011-04-02 14:18 ` [PATCH 2/6] lua-lanes: add recipe for version 2.1.0 and delete the old one Petr Štetiar
2011-04-02 14:18 ` [PATCH 3/6] librs232: add version 1.0.1 and remove " Petr Štetiar
2011-04-02 14:18 ` [PATCH 4/6] lua-rs232: add recipe for version 1.0.1, remove old package and fix stripping Petr Štetiar
2011-04-02 14:18 ` [PATCH 5/6] linux-2.6.36: remove ts72xx support because 2.6.38 is now default Petr Štetiar
2011-04-02 16:08   ` Koen Kooi
2011-04-02 16:31     ` Petr Štetiar [this message]
2011-04-02 14:18 ` [PATCH 6/6] linux-2.6.38: add support for ts72xx and make it default Petr Štetiar
2011-04-10  1:57 ` [PATCH 0/6] RFC: patches I plan to push Khem Raj

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=20110402163101.GA23489@ibawizard.net \
    --to=ynezz@true.cz \
    --cc=openembedded-devel@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