From: Greg KH <greg@kroah.com>
To: Joe Eloff <kagen101@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Simon Horman <horms@verge.net.au>,
devel <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staging: dt3155: fix coding style issues in dt3155_drv.c
Date: Sun, 11 Jul 2010 07:13:07 -0700 [thread overview]
Message-ID: <20100711141307.GA30015@kroah.com> (raw)
In-Reply-To: <1278841771.16713.1.camel@dermezel>
On Sun, Jul 11, 2010 at 11:49:31AM +0200, Joe Eloff wrote:
> On Thu, 2010-07-08 at 13:00 -0700, Greg KH wrote:
> > On Tue, Jul 06, 2010 at 06:53:18PM +0200, Joe Eloff wrote:
> > > I just realised how the commit chaining works after messing it up so I have already
> > > uploaded a 1/2 and 2/2 and now it made another 2/2 for this patch which is different.
> > >
> > > I have realised how it works now and wont mess it up again and have no idea how to reverse chain the
> > > 3 patches.
> > >
> > > This now fixes up all checkpatch.pl issues bar 1.
> >
> > This doesn't apply either :(
> >
> > care to redo all of these against the latest linux-next?
> >
> > thanks,
> >
> > greg k-h
>
> Will redo all against latest tree :(.
>
> Did patches over 3 days, is that why it did not take?
I do not know, sorry.
> Will get up to date and apply the patches again and send.
That would be wonderful.
thanks,
greg k-h
prev parent reply other threads:[~2010-07-11 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 16:53 [PATCH] Staging: dt3155: fix coding style issues in dt3155_drv.c Joe Eloff
2010-07-06 17:25 ` Aldo Cedillo
2010-07-06 17:37 ` Joe Eloff
2010-07-06 21:20 ` Aldo Cedillo
2010-07-07 0:48 ` Simon Horman
2010-07-08 16:31 ` Aldo Cedillo
2010-07-08 20:00 ` Greg KH
2010-07-11 9:49 ` Joe Eloff
2010-07-11 14:13 ` Greg KH [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=20100711141307.GA30015@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=horms@verge.net.au \
--cc=hsweeten@visionengravers.com \
--cc=kagen101@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox