From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org,
Kousik Sanagavarapu <five231003@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-hwmon@vger.kernel.org,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: (subset) [PATCH v2 0/2] lm70 and lm70llp doc link fixes
Date: Mon, 18 Mar 2024 17:27:47 +0000 [thread overview]
Message-ID: <171078286713.91354.1940130554038787719.b4-ty@kernel.org> (raw)
In-Reply-To: <20240318154540.90613-1-five231003@gmail.com>
On Mon, 18 Mar 2024 21:08:33 +0530, Kousik Sanagavarapu wrote:
> Fix links from the documentation and in-code comments pointing to
> datasheets.
>
> Changes since v1:
> - I forgot to fix the links in in-code comments in spi, so do that.
> - New commit to address the same issues in hwmon/lm70 since the spi eval board
> is based on that.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: lm70llp: fix links in doc and comments
commit: 7397175cb7b48f7a3fc699083aa46f1234904c7e
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
prev parent reply other threads:[~2024-03-18 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 13:04 [PATCH] spi: lm70llp: fix links in doc Kousik Sanagavarapu
2024-03-18 15:38 ` [PATCH v2 0/2] lm70 and lm70llp doc link fixes Kousik Sanagavarapu
2024-03-18 15:38 ` [PATCH v2 1/2] spi: lm70llp: fix links in doc and comments Kousik Sanagavarapu
2024-03-18 15:38 ` [PATCH v2 2/2] hwmon: lm70: " Kousik Sanagavarapu
2024-03-18 18:11 ` Guenter Roeck
2024-03-18 18:29 ` Kousik Sanagavarapu
2024-03-18 18:55 ` Guenter Roeck
2024-03-20 17:57 ` Guenter Roeck
2024-03-18 17:27 ` Mark Brown [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=171078286713.91354.1940130554038787719.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=five231003@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®