public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Jones <michael.jones@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] cmd_mac: fix help for 'mac read'
Date: Wed, 27 Jul 2011 16:05:17 +0200	[thread overview]
Message-ID: <4E301B1D.3080900@matrix-vision.de> (raw)
In-Reply-To: <m2mxfzakx6.fsf@ohwell.denx.de>

Hi Detlev,

Thanks for the reply.

On 07/27/2011 03:54 PM, Detlev Zundel wrote:
> 
> Hi Michael,
> 
>> Hi Detlev,
>>
>> On 07/15/2011 05:17 PM, Detlev Zundel wrote:
>>>
>>> Michael Jones <michael.jones@matrix-vision.de> writes:
>>>
>>>> In the only implementation of 'mac read', it doesn't display the
>>>> contents of the eeprom as the help indicated unless compiled with
>>>> DEBUG. It only re-reads the contents of the EEPROM into memory.
>>>> Displaying the contents of the EEPROM is done by passing no
>>>> arguments to 'mac'.
>>>>
>>>> Signed-off-by: Michael Jones <michael.jones@matrix-vision.de>
>>>
>>> Acked-by: Detlev Zundel <dzu@denx.de>
>>>
>>
>> Thanks for the ack. Do you know when I can expect these to get merged in?
> 
> As we currently lack a network maintainer, these patches fall into the
> "and all the rest category" picked up sequentially by Wolfgang.  I
> expect that to happen Real Soon (tm) now.

That's exactly what I wanted to know- it seemed there wasn't a custodian
whom I needed to cc:, and I didn't know who would end up merging them.

> 
> On the other hand, please do not forget that we _intentionally_ allow
> for some time to pass before the patches are merged in order to allow
> for review on the mailing list and to prevent potentially
> merge/revert/change/merge cycles.

Sure, and that makes sense. I just wanted to get a feel for what kind of
time scale that was in general. Obviously these are not important patches.

> 
> Cheers
>   Detlev
> 

thanks,
Michael

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Erhard Meier

  reply	other threads:[~2011-07-27 14:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  8:09 [U-Boot] [PATCH 0/4] cosmetic Michael Jones
2011-07-15  8:09 ` [U-Boot] [PATCH 1/4] cosmetic Michael Jones
2011-07-15 15:15   ` Detlev Zundel
2011-07-15  8:09 ` [U-Boot] [PATCH 2/4] altera: fix printf typo Michael Jones
2011-07-15 15:16   ` Detlev Zundel
2011-07-28 14:33   ` Wolfgang Denk
2011-07-15  8:09 ` [U-Boot] [PATCH 3/4] cmd_mac: cleanup help Michael Jones
2011-07-15 15:16   ` Detlev Zundel
2011-07-28 14:38   ` Wolfgang Denk
2011-07-15  8:09 ` [U-Boot] [PATCH 4/4] cmd_mac: fix help for 'mac read' Michael Jones
2011-07-15 15:17   ` Detlev Zundel
2011-07-27 12:54     ` Michael Jones
2011-07-27 13:54       ` Detlev Zundel
2011-07-27 14:05         ` Michael Jones [this message]
2011-07-28 14:41   ` Wolfgang Denk

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=4E301B1D.3080900@matrix-vision.de \
    --to=michael.jones@matrix-vision.de \
    --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