All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walt Feasel <waltfeasel@gmail.com>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: greg@linuxfoundation.org, linux-kernel-owner@vger.kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Patch procedure
Date: Wed, 16 Nov 2016 02:16:47 -0500	[thread overview]
Message-ID: <20161116071647.GA11563@localhost> (raw)
In-Reply-To: <DB6PR0401MB22647FDED5358E5CF2AB843EE0BF0@DB6PR0401MB2264.eurprd04.prod.outlook.com>

On Tue, Nov 15, 2016 at 08:55:11AM +0000, Ioana Ciornei wrote:
> 
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> > owner@vger.kernel.org] On Behalf Of feas
> > Sent: Monday, November 14, 2016 7:16 PM
> > To: devel@driverdev.osuosl.org; gregkh@linuxfoundation.org; linux-
> > kernel@vger.kernel.org
> > Subject: Patch procedure
> > 
> 
> <snip>
> 
> I know you mentioned the kernel newbies page but just in case you missed this toturial, here is a link https://kernelnewbies.org/FirstKernelPatch. It has all the necessary info for you to submit a proper patch set.
> 
> Ioana C
 Ioana,

Thank you for the link! I had read that but I think this one has fixed what I was 
missing. It has me sending multiple patches together in one email vs sending 
them individualy like I was doing. At least I hope the last one I sent is correct.

https://burzalodowa.wordpress.com/

Walt

      reply	other threads:[~2016-11-16  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 17:16 Patch procedure feas
2016-11-15  7:21 ` Greg KH
2016-11-15  8:55 ` Ioana Ciornei
2016-11-16  7:16   ` Walt Feasel [this message]

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=20161116071647.GA11563@localhost \
    --to=waltfeasel@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@linuxfoundation.org \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.