linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	"leilk.liu" <leilk.liu@mediatek.com>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: Re: [PATCH] spi: remove spi_set_cs_timing()
Date: Tue, 15 Jun 2021 11:20:45 +0200	[thread overview]
Message-ID: <CAMuHMdX34LNV9Q3Yan_7fxS_CzchghYgoCzLTGNW0opKMgv67A@mail.gmail.com> (raw)
In-Reply-To: <162370043177.40904.7910320297802442191.b4-ty@kernel.org>

CC leilk, Alexandru Ardelean

On Mon, Jun 14, 2021 at 9:55 PM Mark Brown <broonie@kernel.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@linux-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

      reply	other threads:[~2021-06-15  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  7:19 [PATCH] spi: remove spi_set_cs_timing() Greg Kroah-Hartman
2021-06-14 19:53 ` Mark Brown
2021-06-15  9:20   ` Geert Uytterhoeven [this message]

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=CAMuHMdX34LNV9Q3Yan_7fxS_CzchghYgoCzLTGNW0opKMgv67A@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=leilk.liu@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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).