refactoring for mask_cache
Get series with b4
b4 am alpine.LFD.2.02.1303202222340.22263@ionosVersions newest first
- v3 Latest1 of 9 patches 0 repliesNew
1 of 9 patches is in this archive. The cover letter announces 9.
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/9 | genirq: add mask_cache and pmask_cache into struct irq_chip_type | +0 | 0 replies |
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 6 lines · Gerlando Falauto
Quoted 5 lines · Jason Cooper
Quoted 4 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.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
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?
Jason had a brain hickup as he told. So please ignore that part :)
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. :-)
Yes, you can give them credit. There are only a few official "....-by:" tags, but you can chose from the inofficial ones:
Suggested-by:
Originally-by:
Original-patch-by:
Requested-by:
Original-idea-by:
Based-on-patch-by:
That's an incomplete list of already in-use tags, but one of those is probably sufficient.
Quoted 3 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?
That needs to go through my tree, really. And please just post it to LKML with the relevant people CC'ed.
Quoted 2 lines
4) About submitting to -stable, I guess it wouldn't make any sense until it gets included upstream
Right. Though I'm a bit concerned about the amount of change involved. So it's simpler to do:
Then let the people who have this problem reply on that patch series with a simple revert of that generic_chip() conversion commit concering their particular subarchitecture instead of forcing a nightmare of complex (and maybe untested) changes onto stable.
Thanks,
tglx