From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pawel Laszczak <pawell@cadence.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Felipe Balbi <balbi@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Lukasz Tyrala <ltyrala@cadence.com>,
Bartosz Folta <bfolta@cadence.com>
Subject: [01/15] Introduce Cadence USBSSP DRD Driver - added gadget.c file.
Date: Thu, 5 Jul 2018 17:14:17 +0200 [thread overview]
Message-ID: <20180705151417.GC10795@kroah.com> (raw)
On Thu, Jul 05, 2018 at 10:15:04AM +0000, Pawel Laszczak wrote:
> > On Tue, Jul 03, 2018 at 08:57:45PM +0100, Pawel Laszczak wrote:
> > > From: Laszczak Pawel <pawell.cadence.com>
> > >
> > > Signed-off-by: Laszczak Pawel <pawell@cadence.com>
> > > ---
> >
> > I can't take patches without any changelog text at all, sorry.
> >
> > Also, your subject lines need work, look at how all other usb patches are
> > written, your long prefix is not really helping out here.
> >
> > > drivers/usb/usbssp/gadget.c | 2082
> > > +++++++++++++++++++++++++++++++++++
> > > 1 file changed, 2082 insertions(+)
> > > create mode 100644 drivers/usb/usbssp/gadget.c
> >
> >
> > Just splitting the driver up by file is hard to review, as you are just dumping
> > individual files on us, not functionality, and we can not review anything until
> > all of them are added. Can you break this up into logical chunks? Make
> > these in a way that is easy to review, would you want to review this patch
> > series in this way?
>
> It's quite large driver and I thought that this form will be better and faster to review.
How can you review it file-by-file without seeing how they all interact?
> I didn't want to prepare too much patches.
Yes, it is more work, but that is how we do kernel development as you
want us to review the code. Just think about what you would want if you
had to review all of this.
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-07-05 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 15:14 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-05 10:15 [01/15] Introduce Cadence USBSSP DRD Driver - added gadget.c file Pawel Laszczak
2018-07-04 9:13 Greg Kroah-Hartman
2018-07-03 19:57 Pawel Laszczak
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=20180705151417.GC10795@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=bfolta@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ltyrala@cadence.com \
--cc=pawell@cadence.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).