All of lore.kernel.org
 help / color / mirror / Atom feed
From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kirkwood: add dir-665 support
Date: Wed, 04 May 2011 09:32:20 +0300	[thread overview]
Message-ID: <4DC0F2F4.6000404@compulab.co.il> (raw)
In-Reply-To: <BANLkTimzZr0vfOdNwVev2A_xoU_1k+SB_w@mail.gmail.com>

On 05/04/11 06:00, Hirundo Cam wrote:
> Hi Mike and Simon
> 
> 2011/5/4 Hirundo Cam <camhirundo@gmail.com>:
>> Hi Mike and Simon,
>>
>> I've send a machine submit to arm-linux, it generated the mach-types as
>>
>> [stripped]
>> mx51_moray              MACH_MX51_MORAY         MX51_MORAY              3484
>> thales_cbc              MACH_THALES_CBC         THALES_CBC              3485
>> bluepoint               MACH_BLUEPOINT          BLUEPOINT               3486
>> dir665                  MACH_DIR665             DIR665                  3487
>>
>> Is this correct for the DIR665 board using mv88f6281 chips?
> 
> Is this implied that I could get rid of the modification to mach-type
> in my patch?

Yes, as soon as mach-types update is pushed into the kernel.

> Thanks!


-- 
Sincerely yours,
Mike.

  reply	other threads:[~2011-05-04  6:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 16:34 [PATCH] kirkwood: add dir-665 support Hirundo Cam
2011-04-27 23:52 ` Hirundo Cam
2011-05-03 15:55 ` Hirundo Cam
2011-05-03 20:51 ` mike at compulab.co.il
2011-05-04  2:36   ` Hirundo Cam
2011-05-04  2:54     ` Hirundo Cam
2011-05-04  3:00       ` Hirundo Cam
2011-05-04  6:32         ` Mike Rapoport [this message]
2011-05-04  8:09       ` Simon Guinot
2011-05-04 13:51         ` Nicolas Pitre
2011-05-05  0:23           ` Hirundo Cam
2011-05-05 15:06           ` Simon Guinot
2011-05-05 19:55             ` Nicolas Pitre
2011-05-06 15:41               ` Simon Guinot
2011-05-06 20:59                 ` Nicolas Pitre
2011-05-04  3:30   ` Hirundo Cam
2011-05-04  6:31     ` Mike Rapoport
2011-05-03 21:14 ` Simon Guinot
     [not found] ` <1304496346-13557-1-git-send-email-camhirundo@gmail.com>
2011-05-04  7:56   ` [PATCH v2] " Hirundo Cam
2011-05-04  8:16   ` Simon Guinot
2011-05-04  9:50     ` saeed bishara
2011-05-05  0:20       ` Hirundo Cam
2011-05-05  7:08         ` saeed bishara
2011-05-05 15:20           ` Hirundo Cam
2011-05-05  0:11     ` Hirundo Cam
2011-05-05  7:50       ` Simon Guinot
2011-05-04  9:23 ` [PATCH] " Jean-Christophe PLAGNIOL-VILLARD

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=4DC0F2F4.6000404@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.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.