From: Felipe Balbi <balbi@ti.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Felipe Balbi <balbi@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND/PATCH 0/2] trivial patches
Date: Thu, 16 Jun 2011 12:37:22 +0300 [thread overview]
Message-ID: <20110616093720.GL12230@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1106161122570.22872@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
Hi,
On Thu, Jun 16, 2011 at 11:23:54AM +0200, Jiri Kosina wrote:
> On Wed, 15 Jun 2011, Felipe Balbi wrote:
>
> > > following patches avoid double semicolons at the end
> > > of module_init/module_exit calls.
> > >
> > > Felipe Balbi (2):
> > > trivial: add missing ; at the end of module_init/module_exit
> > > init: drop trailing semicolon from module_init/module_exit
> >
> > ping... ACK ? NAK ?
>
> I got some conflicts/rejects when applying it right away, so it's now
> sitting in my queue with postponed low-priority patches.
>
> If you'd be able to rebase it on current Linus' tree, it'll help.
I'll do that. Will also check again for any missing ; at the end of
module_init/exit.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-16 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 23:41 Felipe Balbi
2011-05-16 23:41 ` [RESEND/PATCH 1/2] trivial: add missing ; at the end of module_init/module_exit Felipe Balbi
2011-05-16 23:41 ` [RESEND/PATCH 2/2] init: drop trailing semicolon from module_init/module_exit Felipe Balbi
2011-06-15 13:07 ` [RESEND/PATCH 0/2] trivial patches Felipe Balbi
2011-06-16 9:23 ` Jiri Kosina
2011-06-16 9:37 ` Felipe Balbi [this message]
2011-06-16 9:45 ` [PATCH 1/2] trivial: add missing ; at the end of module_init/module_exit Felipe Balbi
2011-06-16 9:45 ` [PATCH 2/2] init: drop trailing semicolon from module_init/module_exit Felipe Balbi
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=20110616093720.GL12230@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=jkosina@suse.cz \
--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
Powered by JetHome