public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: [V2] Add LL TEMAC driver to u-boot and move Emaclite to NET_MULTI
Date: Wed, 07 Oct 2009 16:51:03 +0200	[thread overview]
Message-ID: <4ACCAAD7.8060306@monstr.eu> (raw)
In-Reply-To: <4AC99637.4070907@gmail.com>



Ben Warren wrote:
> Hi Michal,
> 
> Michal Simek wrote:
>> Hi Ben,
>>
>> sorry for head quoting but this is V2.
>> In my net branch is V3 which has some fixes which you reported.
>>
>> Anyway. You want to create two separate patches. I am ok with it.
>> I'll do it and let you know.
>>
>> Thanks,
>> Michal
>>
>>
>>   
> Sorry, I've lost track of where we are with this.  It looks like you've 
> created a net branch in the microblaze tree, but remember that 
> everything has to go through the mailing list before it can be applied.

No worries about. I decided to not to add ll_temac driver to mainline u-boot.
+ yes, I know that all patches should go through mailing list.

Michal

> 
> regards,
> Ben
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2009-10-07 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 10:42 [U-Boot] Xilinx LL temac update monstr at monstr.eu
2009-08-21 10:42 ` [U-Boot] [PATCH] net: [V2] Add LL TEMAC driver to u-boot and move Emaclite to NET_MULTI monstr at monstr.eu
2009-09-14 22:30   ` Ben Warren
2009-09-15  6:23     ` Michal Simek
2009-10-05  6:46       ` Ben Warren
2009-10-07 14:51         ` Michal Simek [this message]
2009-08-25 21:54 ` [U-Boot] Xilinx LL temac update Ben Warren
2009-08-26  7:50   ` Michal Simek
2009-09-02  7:54     ` Michal Simek

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=4ACCAAD7.8060306@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /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