From: gerlando.falauto@keymile.com (Gerlando Falauto)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/9] refactoring for mask_cache
Date: Wed, 20 Mar 2013 18:40:29 +0100 [thread overview]
Message-ID: <5149F48D.3030706@keymile.com> (raw)
In-Reply-To: <20130319115615.GR13280@titan.lakedaemon.net>
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... :-)
On 03/19/2013 12:56 PM, Jason Cooper wrote:
> On Tue, Mar 19, 2013 at 07:44:31AM -0400, Jason Cooper wrote:
>> 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?
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. :-)
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.txt and 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 of
Cc: <stable@vger.kernel.org> # 3.0.x: 123456 first patch
Cc: <stable@vger.kernel.org> # 3.0.x: 123457 second patch
Cc: <stable@vger.kernel.org> # 3.0.x: 123458 third patch
using 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).
Please let me know what to do. Again, it's my first time so please be
gentle. :-)
Thanks again!
Gerlando
>> If you prefer to take it:
>>
>> Acked-by: Jason Cooper <jason@lakedaemon.net>
>
> for the plat-orion/gpio.c bits and if it helps, the gpio-mvebu.c bits.
>
> thx,
>
> Jason.
>
next prev parent reply other threads:[~2013-03-20 17:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 16:10 [PATCH] genirq: allow an alternative setup for the mask cache Holger Brunck
2013-03-14 17:45 ` Simon Guinot
2013-03-15 10:43 ` Holger Brunck
2013-03-15 11:02 ` Thomas Gleixner
2013-03-15 16:26 ` Gerlando Falauto
2013-03-15 19:55 ` Thomas Gleixner
2013-03-14 19:08 ` Thomas Gleixner
2013-03-14 19:42 ` Ezequiel Garcia
2013-03-18 11:05 ` Gerlando Falauto
2013-03-15 19:36 ` [PATCH v2 0/2] refactoring for mask_cache Gerlando Falauto
2013-03-15 19:36 ` [PATCH 1/2] genirq: cosmetic: remove cur_regs Gerlando Falauto
2013-03-15 19:36 ` [PATCH 2/2] genirq: move mask_cache into struct irq_chip_type Gerlando Falauto
2013-03-15 20:47 ` Thomas Gleixner
2013-03-18 7:59 ` Gerlando Falauto
2013-03-18 8:56 ` Thomas Gleixner
2013-03-15 21:25 ` [PATCH v2 0/2] refactoring for mask_cache Andrew Lunn
2013-03-15 23:34 ` Simon Guinot
2013-03-18 14:00 ` [PATCH v3 0/9] " Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 1/9] genirq: cosmetic: remove cur_regs Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 2/9] genirq: add mask_cache and pmask_cache into struct irq_chip_type Gerlando Falauto
2013-03-19 11:32 ` Thomas Gleixner
2013-03-18 14:00 ` [PATCH v3 3/9] gpio: mvebu: convert to usage of *pmask_cache within irq_chip_type Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 4/9] MIPS: JZ4740: " Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 5/9] ARM: SAMSUNG: " Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 6/9] genirq: rename mask_cache to shared_mask_cache Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 7/9] genirq: handle separate mask registers Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 8/9] orion-gpio: enable IRQ_GC_SEPARATE_MASK_REGISTERS Gerlando Falauto
2013-03-18 14:00 ` [PATCH v3 9/9] gpio: mvebu: " Gerlando Falauto
2013-03-18 14:28 ` [PATCH v3 0/9] refactoring for mask_cache Simon Guinot
2013-03-18 14:39 ` Simon Guinot
2013-03-19 10:03 ` Ezequiel Garcia
2013-03-19 10:09 ` Gerlando Falauto
2013-03-19 11:25 ` Ezequiel Garcia
2013-03-19 11:06 ` Jason Cooper
2013-03-19 11:10 ` Gerlando Falauto
2013-03-19 11:44 ` Jason Cooper
2013-03-19 11:56 ` Jason Cooper
2013-03-20 17:40 ` Gerlando Falauto [this message]
2013-03-20 21:42 ` Thomas Gleixner
2013-03-21 10:37 ` Gerlando Falauto
2013-03-21 10:59 ` Simon Guinot
2013-03-19 11:19 ` Ezequiel Garcia
2013-03-21 10:51 ` Simon Guinot
2013-03-21 11:24 ` Gerlando Falauto
2013-04-04 9:31 ` Ezequiel Garcia
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=5149F48D.3030706@keymile.com \
--to=gerlando.falauto@keymile.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).