From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Elliot Berman <quic_eberman@quicinc.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mark Brown <broonie@kernel.org>,
Jiri Slaby <jirislaby@kernel.org>,
Visweswara Tanuku <quic_vtanuku@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: geni-se: Move qcom-geni-se.h to linux/soc/qcom/geni-se.h
Date: Sat, 4 Feb 2023 08:51:59 +0100 [thread overview]
Message-ID: <Y94On1PIUQw4/qX2@kroah.com> (raw)
In-Reply-To: <20230203210133.3552796-1-quic_eberman@quicinc.com>
On Fri, Feb 03, 2023 at 01:01:32PM -0800, Elliot Berman wrote:
> Move include/linux/qcom-geni-se.h to include/linux/soc/qcom/geni-se.h.
> This removes 1 of a few remaining Qualcomm-specific headers into a more
> approciate subdirectory under include/.
>
> Signed-off-by: Elliot Berman <quic_eberman@quicinc.com>
> ---
> drivers/i2c/busses/i2c-qcom-geni.c | 2 +-
> drivers/soc/qcom/qcom-geni-se.c | 2 +-
> drivers/spi/spi-geni-qcom.c | 2 +-
> drivers/tty/serial/qcom_geni_serial.c | 2 +-
> include/linux/{qcom-geni-se.h => soc/qcom/geni-se.h} | 0
> 5 files changed, 4 insertions(+), 4 deletions(-)
> rename include/linux/{qcom-geni-se.h => soc/qcom/geni-se.h} (100%)
Who do you want to take this patch? Through what tree? I can take it
through the tty tree if no one objects, otherwise if someone else is:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2023-02-04 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 21:01 [PATCH] soc: qcom: geni-se: Move qcom-geni-se.h to linux/soc/qcom/geni-se.h Elliot Berman
2023-02-03 21:56 ` Guru Das Srinagesh
2023-02-04 7:04 ` Wolfram Sang
2023-02-04 7:51 ` Greg Kroah-Hartman [this message]
2023-02-09 3:14 ` Bjorn Andersson
2023-02-09 12:27 ` Greg Kroah-Hartman
2023-02-06 18:17 ` Elliot Berman
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=Y94On1PIUQw4/qX2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=jirislaby@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_eberman@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
/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).