From: Guenter Roeck <linux@roeck-us.net>
To: Nick Krause <xerofoify@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
mahesh <mahesh@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Ellerman <michael@ellerman.id.au>,
paulus@samba.org, Anton Blanchard <anton@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Fwd: powerpc allyesconfig fix
Date: Tue, 8 Jul 2014 09:43:52 -0700 [thread overview]
Message-ID: <20140708164352.GA12935@roeck-us.net> (raw)
In-Reply-To: <CAPDOMVitjYMkoLAbwf6oBJg+fpFdKLi+S4hTm6opD27DMC1NDw@mail.gmail.com>
On Tue, Jul 08, 2014 at 12:35:27PM -0400, Nick Krause wrote:
> From: Stephen Rothwell wrote on Tue, Jul 8, 2014 at 2:04 AM
> Subject: Re: powerpc allyesconfig fix
>
> Hi Nicholas,
>
> On Tue, 8 Jul 2014 01:04:09 -0400 Nicholas Krause <xerofoify@gmail.com> wrote:
> >
> > powerpc:allmodconfig has been failing for some time with the following
> > error.
>
> This patch has already bee submitted directly by Guenter, however for
> future reference: when you submit someone else's patch, you should
> include a From line as the first line of the email body containing their
> email address and you should include a Signed-off-by line from yourself.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
>
> Hey Stephen,
> Thanks for the heads up on submitting other people's patches. It would
> be great if you can push this up into Linus's tree
> for the next developer release.
Ben already mentioned that he would pick it up.
Guenter
prev parent reply other threads:[~2014-07-08 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 5:04 powerpc allyesconfig fix Nicholas Krause
2014-07-08 6:04 ` Stephen Rothwell
2014-07-08 16:35 ` Fwd: " Nick Krause
2014-07-08 16:43 ` Guenter Roeck [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=20140708164352.GA12935@roeck-us.net \
--to=linux@roeck-us.net \
--cc=agraf@suse.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=xerofoify@gmail.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).