lkml.org 
[lkml]   [2022]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: (subset) [PATCH 00/49] regmap-irq cleanups and refactoring
    Date
    On Mon, 20 Jun 2022 21:05:55 +0100, Aidan MacDonald wrote:
    > Here's a bunch of cleanups for regmap-irq focused on simplifying the API
    > and generalizing it a bit. It's broken up into three refactors, focusing
    > on one area at a time.
    >
    > * Patches 01 and 02 are straightforward bugfixes, independent of the
    > rest of the series. Neither of the bugs are triggered by in-tree
    > drivers but they might be worth picking up early anyhow.
    >
    > [...]

    Applied to

    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

    Thanks!

    [01/49] regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
    commit: 485037ae9a095491beb7f893c909a76cc4f9d1e7
    [02/49] regmap-irq: Fix offset/index mismatch in read_sub_irq_data()
    commit: 3f05010f243be06478a9b11cfce0ce994f5a0890

    All being well this means that it will be integrated into the linux-next
    tree (usually sometime in the next 24 hours) and sent to Linus during
    the next merge window (or sooner if it is a bug fix), however if
    problems are discovered then the patch may be dropped or reverted.

    You may get further e-mails resulting from automated or manual testing
    and review of the tree, please engage with people reporting problems and
    send followup patches addressing any issues that are reported if needed.

    If any updates are required or you are submitting further changes they
    should be sent as incremental updates against current git, existing
    patches will not be replaced.

    Please add any relevant lists and maintainers to the CCs when replying
    to this mail.

    Thanks,
    Mark

    \
     
     \ /
      Last update: 2022-06-22 17:17    [W:3.204 / U:0.808 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site