| Message ID | 20190115121248.21175-1-brgl@bgdev.pl |
|---|---|
| State | New |
| Headers | show |
| Series | [GIT,PULL] gpio: fixes for v5.0 | expand |
On Tue, Jan 15, 2019 at 1:12 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote: > From: Bartosz Golaszewski <bgolaszewski@baylibre.com> > > The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8: > > Linux 5.0-rc2 (2019-01-14 10:41:12 +1200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-5.0-fixes-for-linus Pulled to my fixes branch. I will rebase and add my signed-off-by I think since I have already sent some other fixes on top of -rc2. But it'll be just as smooth I think. A bit new to this process :D It would be better if we could use the same git tree and just apply and push to the same branches. The ARM SoC does this and sends lock_tree()/unlock_tree() messages to each other on IRC to synchronize! But we could also just try to be optimistic. Occasional pull request like this work too... maybe that is best? Ideas? Yours, Linus Walleij
wt., 15 sty 2019 o 13:59 Linus Walleij <linus.walleij@linaro.org> napisał(a): > > On Tue, Jan 15, 2019 at 1:12 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote: > > > From: Bartosz Golaszewski <bgolaszewski@baylibre.com> > > > > The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8: > > > > Linux 5.0-rc2 (2019-01-14 10:41:12 +1200) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-5.0-fixes-for-linus > > Pulled to my fixes branch. > > I will rebase and add my signed-off-by I think since I have > already sent some other fixes on top of -rc2. > > But it'll be just as smooth I think. A bit new to this process :D > > It would be better if we could use the same git tree and just > apply and push to the same branches. The ARM SoC does > this and sends lock_tree()/unlock_tree() messages to > each other on IRC to synchronize! > > But we could also just try to be optimistic. > > Occasional pull request like this work too... maybe that is > best? > > Ideas? > The way I work with Wolfram Sang is that I send him pull requests just like this and he pulls them into his branch as is. I'm fine with that and think it works well, but if you prefer using a single git tree then we can try to arrange that. Bart
On Tue, Jan 15, 2019 at 2:17 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote: > The way I work with Wolfram Sang is that I send him pull requests just > like this and he pulls them into his branch as is. I'm fine with that > and think it works well, but if you prefer using a single git tree > then we can try to arrange that. This works, let's not fix it if it's not broken :) Yours, Linus Walleij
From: Bartosz Golaszewski <bgolaszewski@baylibre.com> The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8: Linux 5.0-rc2 (2019-01-14 10:41:12 +1200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-5.0-fixes-for-linus for you to fetch changes up to 8d694dcdbbdcfe4f27a52bcc6f2ce733ba5ec53c: gpiolib: fix line event timestamps for nested irqs (2019-01-15 12:51:54 +0100) ---------------------------------------------------------------- GPIO fixes for 5.0 - fix from Roger Quadros for a warning resulting from reusing the same irqchip for multiple pcf857x instances - fix for missing line event timestamp when using nested interrupts ---------------------------------------------------------------- Bartosz Golaszewski (1): gpiolib: fix line event timestamps for nested irqs Roger Quadros (1): gpio: pcf857x: Fix interrupts on multiple instances drivers/gpio/gpio-pcf857x.c | 26 ++++++++++++-------------- drivers/gpio/gpiolib.c | 9 ++++++++- 2 files changed, 20 insertions(+), 15 deletions(-)