From: Alison Schofield <amsfield22@gmail.com>
To: deutschluz@gmail.com
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH] staging: rtl8192e: add more information to Kconfig
Date: Tue, 22 Mar 2016 09:14:09 -0700 [thread overview]
Message-ID: <20160322161408.GA2151@d830.WORKGROUP> (raw)
In-Reply-To: <397c302a-e876-4b6b-9e99-fb7f0f946457@googlegroups.com>
Angel,
Your plain mutt mail looks good. Looks like you may have skipped a step
in formatting the patch. What you have sent is what the file looks
like when I am editing a commit. Try going back thru the tutorial
and recheck the steps...
- if git show HEAD looks good
- then proceed to git format-patch
- and then send the file that git format-patch produces
Hope that helps,
alisons
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/397c302a-e876-4b6b-9e99-fb7f0f946457%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-03-22 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 9:48 [PATCH] staging: rtl8192e: add more information to Kconfig Angel Orejel
2016-03-22 15:39 ` sveta.orlik.code
2016-03-22 16:14 ` Alison Schofield [this message]
2016-03-22 16:22 ` sveta.orlik.code
2016-03-22 17:55 ` Angel Orejel
2016-03-22 21:13 ` [Outreachy kernel] " Greg KH
[not found] ` <CAGLzxArcwTX1VnkSQs=wr_hpB=uoKPcPQ-WVMZXCDc1M8ZAmOg@mail.gmail.com>
[not found] ` <20160324025609.GB19662@kroah.com>
2016-03-24 5:09 ` Angel Orejel
2016-03-24 6:23 ` Julia Lawall
2016-03-24 13:56 ` Greg KH
2016-03-25 7:38 ` Angel Orejel
2016-03-25 7:45 ` Julia Lawall
2016-03-25 7:49 ` Angel Orejel
2016-03-25 7:56 ` Julia Lawall
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=20160322161408.GA2151@d830.WORKGROUP \
--to=amsfield22@gmail.com \
--cc=deutschluz@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.