From: Mark Brown <broonie@kernel.org>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: linux-gpio@vger.kernel.org, ath10k@lists.infradead.org,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
dri-devel@lists.freedesktop.org, linux-input@vger.kernel.org,
linux-pm@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-rdma@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 00/17] spelling.txt: /decriptors/descriptors/
Date: Tue, 16 Jun 2020 00:41:15 +0100 [thread overview]
Message-ID: <159226447507.27673.16785893373246037922.b4-ty@kernel.org> (raw)
In-Reply-To: <20200609124610.3445662-1-kieran.bingham+renesas@ideasonboard.com>
On Tue, 9 Jun 2020 13:45:53 +0100, Kieran Bingham wrote:
> I wouldn't normally go through spelling fixes, but I caught sight of
> this typo twice, and then foolishly grepped the tree for it, and saw how
> pervasive it was.
>
> so here I am ... fixing a typo globally... but with an addition in
> scripts/spelling.txt so it shouldn't re-appear ;-)
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] regulator: Fix trivial spelling
commit: d3f3723387f97118c337689fc73e4199fb4331ce
[2/2] regulator: gpio: Fix trivial spelling
commit: 1f0b740004f09d2f1b716fd6c2fdca81004ded05
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
next prev parent reply other threads:[~2020-06-15 23:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 12:45 [PATCH 00/17] spelling.txt: /decriptors/descriptors/ Kieran Bingham
2020-06-09 12:45 ` [PATCH 01/17] arch: arm: mach-davinci: Fix trivial spelling Kieran Bingham
2020-06-09 12:45 ` [PATCH 02/17] drivers: infiniband: " Kieran Bingham
2020-06-09 15:53 ` Dennis Dalessandro
2020-06-09 12:45 ` [PATCH 03/17] drivers: gpio: " Kieran Bingham
2020-06-15 8:16 ` Bartosz Golaszewski
2020-06-09 12:45 ` [PATCH 04/17] drivers: mtd: nand: raw: " Kieran Bingham
2020-06-15 9:00 ` Miquel Raynal
2020-06-09 12:45 ` [PATCH 05/17] drivers: net: " Kieran Bingham
2020-07-15 10:22 ` Kalle Valo
[not found] ` <20200715102209.C9012C433A1@smtp.codeaurora.org>
2020-07-15 12:52 ` Kieran Bingham
2020-06-09 12:45 ` [PATCH 06/17] drivers: scsi: " Kieran Bingham
2020-06-09 12:46 ` [PATCH 07/17] drivers: usb: " Kieran Bingham
2020-06-18 8:21 ` Greg Kroah-Hartman
2020-06-18 8:52 ` Kieran Bingham
2020-06-18 9:43 ` Greg Kroah-Hartman
2020-06-09 12:46 ` [PATCH 08/17] drivers: gpu: drm: " Kieran Bingham
2020-06-10 15:32 ` Daniel Vetter
2020-06-09 12:46 ` [PATCH 09/17] drivers: regulator: " Kieran Bingham
2020-06-09 12:50 ` Mark Brown
2020-06-09 12:46 ` [PATCH 10/17] drivers: input: joystick: " Kieran Bingham
2020-06-09 12:46 ` [PATCH 11/17] drivers: infiniband: " Kieran Bingham
2020-06-09 15:54 ` Dennis Dalessandro
2020-06-09 16:04 ` Kieran Bingham
2020-06-09 12:46 ` [PATCH 12/17] drivers: devfreq: " Kieran Bingham
2020-07-03 0:38 ` Chanwoo Choi
2020-06-09 12:46 ` [PATCH 13/17] include: dynamic_debug.h: " Kieran Bingham
2020-06-09 12:46 ` [PATCH 14/17] kernel: trace: " Kieran Bingham
2020-06-09 12:46 ` [PATCH 15/17] mm: " Kieran Bingham
2020-06-09 14:03 ` David Hildenbrand
2020-06-09 14:34 ` [PATCH v2] mm/balloon_compaction: " Kieran Bingham
2020-06-09 16:32 ` Souptick Joarder
2020-06-09 16:35 ` Souptick Joarder
2020-06-09 16:37 ` Michael S. Tsirkin
2020-06-10 9:00 ` Sergei Shtylyov
2020-06-10 9:06 ` Kieran Bingham
2020-06-09 12:46 ` [PATCH 16/17] regulator: gpio: " Kieran Bingham
2020-06-09 12:46 ` [PATCH 17/17] scripts/spelling.txt: Add descriptors correction Kieran Bingham
2020-06-09 16:08 ` Joe Perches
2020-06-10 9:09 ` Kieran Bingham
2020-06-15 18:58 ` [PATCH 00/17] spelling.txt: /decriptors/descriptors/ Jason Gunthorpe
2020-06-15 23:41 ` Mark Brown [this message]
2020-06-16 3:59 ` Martin K. Petersen
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=159226447507.27673.16785893373246037922.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).