From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Sandeep Maheswaram (Temp)" <quic_c_sanm@quicinc.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Pawel Laszczak <pawell@cadence.com>,
Peter Chen <peter.chen@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Aswath Govindraju <a-govindraju@ti.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_pkondeti@quicinc.com,
quic_ppratap@quicinc.com
Subject: Re: [PATCH v2 2/3] usb: xhci: Remove unwanted header inclusion
Date: Mon, 21 Mar 2022 10:34:16 +0100 [thread overview]
Message-ID: <YjhGmJYbATchV+Zs@kroah.com> (raw)
In-Reply-To: <adb12afc-4591-4a96-9988-e0d6a2ceb060@quicinc.com>
On Mon, Mar 21, 2022 at 02:47:08PM +0530, Sandeep Maheswaram (Temp) wrote:
> Hi Greg,
>
> On 3/18/2022 5:31 PM, Greg Kroah-Hartman wrote:
> > On Tue, Mar 01, 2022 at 03:58:26PM +0530, Sandeep Maheswaram wrote:
> > > Remove the header file and forward declare struct usb_hcd.
> > Why?
>
> This was done to address below comment in previous version
>
> https://patchwork.kernel.org/project/linux-arm-msm/patch/1644949454-814-2-git-send-email-quic_c_sanm@quicinc.com/#24739885
Then EXPLAIN THAT in the changelog text. Don't make us guess.
Please read the kernel documentation for how to write a good changelog
text. This single sentance does not follow the guidelines at all.
>
>
> >
> > > Signed-off-by: Sandeep Maheswaram <quic_c_sanm@quicinc.com>
> > > ---
> > > include/linux/usb/xhci-plat.h | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/include/linux/usb/xhci-plat.h b/include/linux/usb/xhci-plat.h
> > > index 906e907..576e400 100644
> > > --- a/include/linux/usb/xhci-plat.h
> > > +++ b/include/linux/usb/xhci-plat.h
> > > @@ -9,7 +9,8 @@
> > > #define _XHCI_PLAT_H
> > > #include <linux/types.h>
> > > -#include <linux/usb/hcd.h>
> > > +
> > > +struct usb_hcd;
> > > struct xhci_plat_priv {
> > > const char *firmware_name;
> > > --
> > > 2.7.4
> > >
> > Where did this come from? Is this fixing a build breakage from a
> > previous patch? If not, why is this needed?
> >
> > confused,
> >
> > greg k-h
>
> There wasn't any build breakage.
>
> This was done to address below comment in previous version
>
> https://patchwork.kernel.org/project/linux-arm-msm/patch/1644949454-814-2-git-send-email-quic_c_sanm@quicinc.com/#24739885
Again, how were we supposed to know any of this?
Please read the documentation again for how to do this properly.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-21 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 10:28 [PATCH v2 0/3] Refactor xhci quirks and plat private data Sandeep Maheswaram
2022-03-01 10:28 ` [PATCH v2 1/3] usb: xhci: refactor " Sandeep Maheswaram
2022-03-18 12:00 ` Greg Kroah-Hartman
2022-03-01 10:28 ` [PATCH v2 2/3] usb: xhci: Remove unwanted header inclusion Sandeep Maheswaram
2022-03-18 12:01 ` Greg Kroah-Hartman
2022-03-21 9:17 ` Sandeep Maheswaram (Temp)
2022-03-21 9:34 ` Greg Kroah-Hartman [this message]
2022-03-01 10:28 ` [PATCH v2 3/3] usb: dwc: host: add xhci_plat_priv quirk XHCI_SKIP_PHY_INIT Sandeep Maheswaram
2022-03-18 12:01 ` Greg Kroah-Hartman
2022-03-21 6:09 ` Sandeep Maheswaram (Temp)
2022-03-17 5:47 ` [PATCH v2 0/3] Refactor xhci quirks and plat private data Sandeep Maheswaram (Temp)
2022-03-18 11:59 ` Greg Kroah-Hartman
2022-03-21 6:21 ` Sandeep Maheswaram (Temp)
2022-03-22 15:53 ` Mathias Nyman
2022-03-23 3:07 ` Pavan Kondeti
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=YjhGmJYbATchV+Zs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a-govindraju@ti.com \
--cc=balbi@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mka@chromium.org \
--cc=pawell@cadence.com \
--cc=peter.chen@kernel.org \
--cc=quic_c_sanm@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=rogerq@kernel.org \
--cc=swboyd@chromium.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).