refactoring for mask_cache
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/20 of 9 patches 0 repliesNew
- v3 posting 1/20 of 9 patches 0 repliesSuperseded
- v20 of 2 patches 0 repliesSuperseded
Patches in v3 posting 2/2 No applies recorded yet
None of the 9 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/9] refactoring for mask_cache
Quoted 22 lines · Gerlando Falauto
Hi,
sorry about the delay (been busy with other stuff). First of all thanks for your hints. I have some questions. This is my first time, so please be gentle... :-)
Quoted 9 lines · Jason Cooper
Quoted 5 lines · Jason Cooper
Those commit IDs are going to change once LinusW (I presume) applies them to his tree, so he'll have to edit each commit message to point the the correct commit.
LinusW, do you want me to handle this?
Never mind, coffee underflow to
/dev/brain. One drawback to mutt, can't view thread while typing messages...1) I had no idea who LinusW is, I assume Linus Walleij who should be the maintainer of linux-gpio. And linux-gpio should have nothing to do with this discussion... so I should assume you never mentioned him, right?
Quoted 4 lines
2) About the SOB part... most of this is inspired by Simon's original (single) patch and Holger's reworking. Should they be given credit or not? If yes, how? If I don't get an answer I would just assume no and I'll take all the blame and credit all by myself. :-)
Please drop all the SOBs with my name. Except for giving up a patch almost two years, I am not involved in this patch series development. I am quite sure there is no credit in that :)
Thanks.
Simon
Quoted 29 lines
3) Jason, did you mean you would pull it to
http://git.infradead.org/users/jcooper/linux.git? Shall I change the SOB lines and resubmit? Or should I submit it somewhere else instead?4) About submitting to -stable, I guess it wouldn't make any sense until it gets included upstream
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ so to speak). Is that right?
Or at least to jcooper's tree, through which it should eventually make it mainline through a merge (therefore keeping its commit-id). That right?I did read
Documentation/stable_kernel_rules.txtand what I understand is that it would be enough to submit to
stable at vger.kernel.org only the last one, while providing a list ofCc <[email protected]> # 3.0.x: 123456 first patchCc <[email protected]> # 3.0.x: 123457 second patchCc <[email protected]> # 3.0.x: 123458 third patchusing the mainstream (or jcooper's) commit IDs.
I don't know whether I'd have to repeat that for each version (3.0 will include only a subset of this series, while 3.7 and following will need the whole nine yards, and what's in between... well, something in between).
Quoted 16 lines
Please let me know what to do. Again, it's my first time so please be gentle. :-)
Thanks again!
GerlandoQuoted 10 lines
Quoted 3 lines
If you prefer to take it:
Acked-by Jason Cooper <[email protected]>for the
plat-orion/gpio.cbits and if it helps, thegpio-mvebu.cbits.thx,
Jason.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130321/736911a4/attachment.sig>