From: Greg KH <greg@kroah.com>
To: Klaas Neirinck <klaas.neirinck@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
Klaas Neirinck <klaas.nerinck@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/10] Staging: tidspbridge: fixed a brace coding style issue
Date: Fri, 18 Feb 2011 21:34:17 -0800 [thread overview]
Message-ID: <20110219053417.GB21529@kroah.com> (raw)
In-Reply-To: <4D5F29D9.1080601@gmail.com>
On Sat, Feb 19, 2011 at 03:24:25AM +0100, Klaas Neirinck wrote:
> On 18/02/2011 22:27, Greg KH wrote:
> >On Thu, Feb 17, 2011 at 03:58:45AM +0100, Klaas Neirinck wrote:
> >>Fixed a coding style issue.
> >>
> >>Signed-off-by: Klaas Neirinck<klaas.nerinck@gmail.com>
> >This doesn't apply at all to the linux-next tree, what did you do it
> >against?
> >
> >confused,
> >
> >greg k-h
> I did it against
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> as shown in http://www.youtube.com/fosdemtalks#p/u/0/LLBrBBImJt4
> great talk btw!
Thanks, but the patches really need to be against linux-next, which I
didn't really spell out very well in that talk, sorry. linux-next
contains all of the patches that others have sent me that are queued up
for the next kernel release after this one.
Hope this helps,
greg k-h
prev parent reply other threads:[~2011-02-19 5:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 2:58 [PATCH 01/10] Staging: tidspbridge: fixed a brace coding style issue Klaas Neirinck
2011-02-17 2:58 ` [PATCH 02/10] Staging: tidspbridge: fixed an include issue changing asm/atomic.h to linux/atomic.h Klaas Neirinck
2011-02-17 2:58 ` [PATCH 03/10] Staging: tidspbridge: fixed unnecessary whitespaces before quoted newlines Klaas Neirinck
2011-02-17 2:58 ` [PATCH 04/10] Staging: tidspbridge: fixed indent coding style issue Klaas Neirinck
2011-02-17 2:58 ` [PATCH 05/10] Staging: tidspbridge: fixed extern in .c file Klaas Neirinck
2011-02-17 2:58 ` [PATCH 06/10] Staging: tidspbridge: fixed spaces before tabs issues Klaas Neirinck
2011-02-17 2:58 ` [PATCH 07/10] Staging: tidspbridge: fixed spaces at the start of a line coding style issues Klaas Neirinck
2011-02-17 2:58 ` [PATCH 08/10] Staging: tidspbridge: fixed missing space after struct definition Klaas Neirinck
2011-02-17 2:58 ` [PATCH 09/10] Staging: tidspbridge: fixed spaces after '*' style issues Klaas Neirinck
2011-02-17 2:58 ` [PATCH 10/10] Staging: tidspbridge: fixed casting style issue Klaas Neirinck
2011-02-18 21:27 ` [PATCH 01/10] Staging: tidspbridge: fixed a brace coding " Greg KH
2011-02-19 2:24 ` Klaas Neirinck
2011-02-19 5:34 ` 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=20110219053417.GB21529@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=klaas.neirinck@gmail.com \
--cc=klaas.nerinck@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