[U-Boot] : sf: spansion: Add support for S25FL128S
Hi,
Request for few details here.
I am not understanding why this is applied on tree, [even i din't see the applied note on mailing list, may be i am missing] I was asked Xie Xiaobo to send v2 fo updating the name to - .name = "S25FL129P_64K/S25FL128S", + .name = "S25FL129P_64K/S25FL128S_64K",
Even i sent a patch on be of Xie Xiaobo http://patchwork.ozlabs.org/patch/247607/
Any comments, was the notion i used on patch was wrong.
-- Thanks, Jagan.
On Jun 10, 2013, at 1:34 PM, Jagan Teki wrote:
Hi,
Request for few details here.
I am not understanding why this is applied on tree, [even i din't see the applied note on mailing list, may be i am missing]
I've been bad about sending a message when I apply the patches. I'm hesitant to do so when I apply dozens of patches at a time, as it adds significant overhead to each patch application. Finding the patch email in my inbox is time-consuming.
I was asked Xie Xiaobo to send v2 fo updating the name to
.name = "S25FL129P_64K/S25FL128S",
.name = "S25FL129P_64K/S25FL128S_64K",Even i sent a patch on be of Xie Xiaobo http://patchwork.ozlabs.org/patch/247607/
Any comments, was the notion i used on patch was wrong.
Sorry, York Sun submitted a version of the original patch back in March, and it got applied May 24. I see now that you got a version in February, which Xiaobo responded to May 30. I didn't realize it was under your domain, so I apologize (Ah, I see you were added to the list probably just after I looked for who was in charge of spi).
Feel free to revert the patch, or modify, as you see fit, and I will avoid applying patches to spi in the future. :)
Andy
On 06/11/2013 05:14:53 PM, Fleming Andy-AFLEMING wrote:
On Jun 10, 2013, at 1:34 PM, Jagan Teki wrote:
Hi,
Request for few details here.
I am not understanding why this is applied on tree, [even i din't
see
the applied note on mailing list, may be i am missing]
I've been bad about sending a message when I apply the patches. I'm hesitant to do so when I apply dozens of patches at a time, as it adds significant overhead to each patch application. Finding the patch email in my inbox is time-consuming.
You can reply directly to the patchwork mbox (assuming that's where you're getting the patch from, if not your inbox).
-Scott
On Jun 11, 2013, at 5:17 PM, Scott Wood wrote:
On 06/11/2013 05:14:53 PM, Fleming Andy-AFLEMING wrote:
On Jun 10, 2013, at 1:34 PM, Jagan Teki wrote:
Hi,
Request for few details here.
I am not understanding why this is applied on tree, [even i din't see the applied note on mailing list, may be i am missing]
I've been bad about sending a message when I apply the patches. I'm hesitant to do so when I apply dozens of patches at a time, as it adds significant overhead to each patch application. Finding the patch email in my inbox is time-consuming.
You can reply directly to the patchwork mbox (assuming that's where you're getting the patch from, if not your inbox).
via something like mutt? I will make an effort to do that.
On Tue, Jun 11, 2013 at 10:14:53PM +0000, Fleming Andy-AFLEMING wrote:
On Jun 10, 2013, at 1:34 PM, Jagan Teki wrote:
Hi,
Request for few details here.
I am not understanding why this is applied on tree, [even i din't see the applied note on mailing list, may be i am missing]
I've been bad about sending a message when I apply the patches. I'm hesitant to do so when I apply dozens of patches at a time, as it adds significant overhead to each patch application. Finding the patch email in my inbox is time-consuming.
FWIW, patchwork bundles help me here. I make one for what I'm going to apply then throw that at both git am and mutt (and folder-hooks to make sure I'm using the right email, etc)..
participants (4)
-
Fleming Andy-AFLEMING -
Jagan Teki -
Scott Wood -
Tom Rini