From: Ulf Samuelsson <ulfs@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Atmel DataFlash hooks.
Date: Fri, 26 Jan 2007 22:21:59 +0100 [thread overview]
Message-ID: <012801c74192$289ae920$01c4af0a@atmel.com> (raw)
In-Reply-To: 528646bc0701261227hb546f4fx72efde9caa23c1c6@mail.gmail.com
>> Now with the new approach to introducing patches,
>> I think the SAM9 patches should be sent in soon
>> and you will have a significant number of boards
>> that will break if you screw up.
>
> Just because I write the patches doesn't mean they get accepted. They
> need to be acked by someone who has tested them first. I'm offering
> to take on the workload of writing the patches, but I cannot take on
> the testing. A number of the changes that I'm making right now (not
> just DataFlash) affect every single board, but I cannot test them all.
> Best I can do is make sure it works on the handful of boards I do
> have, post the patches for others to test, and only request inclusion
> in mainline when nobody reports problems with them.
>
I beleive a more proper approach is that
If you cannot test the patches yourself, then you need to wait
until someone confirms that the patch is actually working.
If noone tests the patch, that is an indication that noone is interested.
>>> For the stuff that *is* in mainline, I will of course make sure that
>>> the patches compile, but I cannot test them. I do not have the
>>> hardware to do so, nor will I spend the time to test boards that I
>>> have absolutely no involvement with.
>>>
>>
>> That sound like a great idea, introduce significant modifications
>> without testing...
>
> The mods I'm interested in are the architectural changes which I can
> and will test. The DataFlash changes are collateral damage. The
> alternative for me is to break dataflash support without even
> attempting to providing a solution.
>
>>
>> I think you should spend time on modifying things you *can* test.
>
> Then how does *anybody* attempt to fix common code? Nobody can test
> all platforms.
No, but you started off by saying you specifically are focusing on
dataflash,
and then you need to test on the primary target for the dataflash
which is the AT91 series.
> Cheers,
> g.
Best Regards,
Ulf Samuelsson
next prev parent reply other threads:[~2007-01-26 21:21 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 8:44 [U-Boot-Users] Atmel DataFlash hooks Grant Likely
2007-01-26 9:42 ` Peter.Pearse
2007-01-26 9:46 ` [U-Boot-Users] How to skip network driver? Rui.Zhou at nokia.com
2007-01-26 9:56 ` w.wegner at astro-kom.de
2007-01-26 14:38 ` Wolfgang Denk
2007-01-26 13:53 ` [U-Boot-Users] Atmel DataFlash hooks Wolfgang Denk
2007-01-26 19:24 ` Grant Likely
2007-01-26 21:27 ` Wolfgang Denk
2007-01-26 22:35 ` Grant Likely
[not found] ` <000001c7416f$fa61fed0$01c4af0a@atmel.com>
2007-01-26 19:02 ` Grant Likely
[not found] ` <02eb01c74180$c4911410$01c4af0a@atmel.com>
2007-01-26 20:27 ` Grant Likely
2007-01-26 21:21 ` Ulf Samuelsson [this message]
2007-01-26 22:40 ` Grant Likely
2007-01-26 23:01 ` Ulf Samuelsson
2007-01-26 23:46 ` Grant Likely
2007-01-27 9:44 ` Ulf Samuelsson
2007-01-29 10:49 ` Stefan Roese
2007-01-29 13:44 ` Peter.Pearse
2007-01-29 14:47 ` Stefan Roese
2007-01-29 16:03 ` Wolfgang Denk
2007-01-29 10:33 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2007-01-26 16:45 Peter.Pearse
2007-01-26 19:11 ` Grant Likely
2007-01-26 21:25 ` Wolfgang Denk
2007-01-26 22:34 ` Grant Likely
2007-01-27 0:42 ` Wolfgang Denk
2007-01-27 1:52 ` Grant Likely
2007-01-27 13:34 ` Andreas Schweigstill
2007-01-27 16:36 ` Wolfgang Denk
2007-01-27 17:04 ` Andreas Schweigstill
2007-01-27 17:17 ` Ulf Samuelsson
2007-01-28 14:39 ` Wolfgang Denk
2007-01-29 1:32 ` Andreas Schweigstill
2007-01-29 12:52 ` Wolfgang Denk
2007-01-27 22:19 ` Grant Likely
2007-01-28 1:47 ` J. William Campbell
2007-01-28 15:17 ` Wolfgang Denk
2007-01-28 22:21 ` J. William Campbell
2007-01-28 22:50 ` Wolfgang Denk
2007-01-29 2:50 ` Grant Likely
2007-01-29 13:07 ` Wolfgang Denk
2007-01-29 21:06 ` Haavard Skinnemoen
2007-01-29 22:57 ` Ulf Samuelsson
2007-01-29 23:55 ` Wolfgang Denk
2007-01-30 0:28 ` Haavard Skinnemoen
2007-01-30 1:03 ` Wolfgang Denk
2007-01-30 1:16 ` Haavard Skinnemoen
2007-01-30 22:23 ` Wolfgang Denk
2007-01-30 6:52 ` Ulf Samuelsson
2007-01-31 7:44 ` Tolunay Orkun
2007-01-29 3:17 ` J. William Campbell
2007-01-29 7:35 ` Ulf Samuelsson
2007-01-29 13:36 ` Wolfgang Denk
2007-01-29 13:29 ` Wolfgang Denk
2007-01-29 20:45 ` J. William Campbell
2007-01-29 21:48 ` Wolfgang Denk
2007-01-29 23:03 ` J. William Campbell
2007-01-30 0:01 ` Wolfgang Denk
2007-01-29 23:08 ` Ulf Samuelsson
2007-01-30 0:48 ` J. William Campbell
2007-01-30 1:06 ` Wolfgang Denk
2007-01-30 6:55 ` Ulf Samuelsson
2007-01-31 17:11 ` Grant Likely
2007-01-31 17:37 ` Ulf Samuelsson
2007-01-31 21:55 ` Wolfgang Denk
2007-01-31 23:13 ` Ulf Samuelsson
2007-01-31 23:50 ` Grant Likely
2007-02-01 0:06 ` Wolfgang Denk
2007-02-01 2:46 ` Tolunay Orkun
2007-01-29 11:10 ` Stefan Roese
2007-01-29 2:27 ` Grant Likely
2007-01-28 15:01 ` Wolfgang Denk
2007-01-29 2:33 ` Grant Likely
2007-01-29 7:49 ` Ulf Samuelsson
2007-01-29 13:38 ` Wolfgang Denk
[not found] ` <528646bc0701310848x4c63cf53gd228f860c0fd0444@mail.gmail.com>
2007-01-31 16:50 ` Grant Likely
2007-02-01 12:40 ` Andreas Schweigstill
2007-01-29 12:56 ` Wolfgang Denk
2007-01-29 10:43 ` Stefan Roese
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='012801c74192$289ae920$01c4af0a@atmel.com' \
--to=ulfs@atmel.com \
--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