public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Vladimir Stankovic <vladimir.stankovic@displaylink.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Petar Kovacevic <petar.kovacevic@displaylink.com>,
	Nikola Simic <nikola.simic@displaylink.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Marko Miljkovic <marko.miljkovic@displaylink.com>,
	Stefan Lugonjic <stefan.lugonjic@displaylink.com>
Subject: Re: [External] Re: staging: Add MA USB Host driver
Date: Wed, 22 Jan 2020 09:49:21 +0100	[thread overview]
Message-ID: <20200122084921.GA2420736@kroah.com> (raw)
In-Reply-To: <98df2373-6f19-df36-c78c-e0384ddb8730@displaylink.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, Jan 22, 2020 at 08:16:09AM +0000, Vladimir Stankovic wrote:
> Hi Greg,
> 
> It was section 2.5 of the kernel development process, "staging trees".
> In particular, statement "where many sub-directories for drivers or 
> filesystems that are on their way to being added to the kernel tree 
> live" caught our attention.
> 
> Now, by reading it once again, I see that the rest of the section is in 
> line with your comment.
> 
> We'll address all comments received so far, and resubmit patch onto 
> appropriate repository. With that being said, is USB subsystem tree 
> (drivers/usb within usb.git repo) correct one? Please, advise.

If this is a USB host driver, then yes, drivers/usb/host/ would be the
correct location for this.

Note, at first glance, there is a bunch of work to do on this to get it
into "real" mergable shape.  Be sure to at the very least get it
'checkpatch.pl clean' before submitting it, that will help out a lot, if
it is not already done.

thanks,

greg k-h

  reply	other threads:[~2020-01-22  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR10MB19659B32E563620B4D63AF1A91320@VI1PR10MB1965.EURPRD10.PROD.OUTLOOK.COM>
     [not found] ` <VI1PR10MB1965A077526FE296608D5B1191320@VI1PR10MB1965.EURPRD10.PROD.OUTLOOK.COM>
2020-01-20  9:30   ` staging: Add MA USB Host driver Vladimir Stankovic
2020-01-21  8:01     ` Dan Carpenter
2020-01-21  8:13     ` Dan Carpenter
2020-01-22  7:03     ` gregkh
2020-01-22  7:40       ` [External] " Vladimir Stankovic
2020-01-22  7:48         ` gregkh
2020-01-22  8:16           ` Vladimir Stankovic
2020-01-22  8:49             ` gregkh [this message]
2020-01-22  9:07               ` Vladimir Stankovic

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=20200122084921.GA2420736@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marko.miljkovic@displaylink.com \
    --cc=nikola.simic@displaylink.com \
    --cc=petar.kovacevic@displaylink.com \
    --cc=stefan.lugonjic@displaylink.com \
    --cc=vladimir.stankovic@displaylink.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