linux-kernel - Re: [PATCH] spi: remove spi_set_cs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMuHMdX34LNV9Q3Yan_7fxS_CzchghYgoCzLTGNW0opKMgv67A@mail.gmail.com>
Date:   Tue, 15 Jun 2021 11:20:45 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-spi <linux-spi@...r.kernel.org>,
        "leilk.liu" <leilk.liu@...iatek.com>,
        Alexandru Ardelean <alexandru.ardelean@...log.com>
Subject: Re: [PATCH] spi: remove spi_set_cs_timing()

CC leilk, Alexandru Ardelean

On Mon, Jun 14, 2021 at 9:55 PM Mark Brown <broonie@...nel.org> wrote:
> On Wed, 9 Jun 2021 09:19:18 +0200, Greg Kroah-Hartman wrote:
> > No one seems to be using this global and exported function, so remove it
> > as it is no longer needed.
>
> Applied to
>
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/1] spi: remove spi_set_cs_timing()
>       commit: 4ccf359849ce709f4bf0214b4b5b8b6891d38770
>
> 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.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds