public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: christian@lkamp.de, neil@brown.name, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ralink-gdma: Convert unsigned to unsigned int
Date: Sun, 24 Mar 2019 13:11:14 +0100	[thread overview]
Message-ID: <20190324121114.GA5772@kroah.com> (raw)
In-Reply-To: <20190324093748.GA15691@bharath12345-Inspiron-5559>

On Sun, Mar 24, 2019 at 03:07:48PM +0530, Bharath Vedartham wrote:
> On Sun, Mar 24, 2019 at 09:58:42AM +0100, Greg KH wrote:
> > On Sat, Mar 23, 2019 at 05:04:44PM +0530, Bharath Vedartham wrote:
> > > Fix the checkpatch.pl warning: "Use unsigned int instead of unsigned".
> > > 
> > > Signed-off-by: Bharath Vedartham <linux.bhar@gmail.com>
> > > ---
> > >  drivers/staging/ralink-gdma/ralink-gdma.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > This patch also does not apply at all :(
> 
> I have been working on linus's branch and not the staging branch. I
> thought that linus's branch would have the latest updates and would be
> the latest branch :( . Is it a problem if I use linus's branch for
> staging drivers?

Yes, if you want to do kernel development, you always need to work off
of the subsystem tree that you are wanting to contribute to, or off of
linux-next.  Development trees can often be 3 months ahead of Linus's
tree depending on the time of the merge window.

The tree should always be listed in the MAINTAINERS file for what one to
use.

hope this helps,

greg k-h

  reply	other threads:[~2019-03-24 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23 11:34 [PATCH] staging: ralink-gdma: Convert unsigned to unsigned int Bharath Vedartham
2019-03-24  8:58 ` Greg KH
2019-03-24  9:37   ` Bharath Vedartham
2019-03-24 12:11     ` Greg KH [this message]
2019-03-24  9:49   ` Bharath Vedartham

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=20190324121114.GA5772@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=christian@lkamp.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.bhar@gmail.com \
    --cc=neil@brown.name \
    /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