From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Alan Cox <alan@linux.intel.com>,
"Gujulan Elango, Hari Prasath (H.)" <hgujulan@visteon.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"somyaanand214@gmail.com" <somyaanand214@gmail.com>,
"iskaranth@gmail.com" <iskaranth@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: i2o: Remove unwanted semicolon
Date: Thu, 30 Apr 2015 23:25:48 +0100 [thread overview]
Message-ID: <20150430232548.0ee0a0a5@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20150430141406.GA8230@kroah.com>
On Thu, 30 Apr 2015 16:14:06 +0200
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org> wrote:
> On Thu, Apr 23, 2015 at 04:09:28PM +0100, Alan Cox wrote:
> > On Thu, 2015-04-23 at 13:43 +0000, Gujulan Elango, Hari Prasath (H.)
> > wrote:
> > > This patch removes unwanted semicolon around close braces of code blocks
> >
> >
> > The i2o driver moved into staging ready to be deleted unless someone
> > steps up with hardware willing to maintain it (which is rather
> > unlikely).
>
> I think it's now time to delete these, want me to do that for 4.2? I
> can queue that up in my tree now, so that we don't see any more cleanup
> patches being made for them?
Yeah I think it can go....
next prev parent reply other threads:[~2015-04-30 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 13:43 [PATCH] staging: i2o: Remove unwanted semicolon Gujulan Elango, Hari Prasath (H.)
2015-04-23 15:09 ` Alan Cox
2015-04-30 14:14 ` gregkh
2015-04-30 16:35 ` hari prasath
2015-05-01 7:18 ` Dan Carpenter
2015-05-01 7:33 ` Dan Carpenter
2015-04-30 22:25 ` One Thousand Gnomes [this message]
2015-05-01 7:41 ` gregkh
2015-05-01 9:28 ` Alan Cox
2015-05-01 14:16 ` gregkh
2015-05-01 18:53 ` Alan Cox
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=20150430232548.0ee0a0a5@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hgujulan@visteon.com \
--cc=iskaranth@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=somyaanand214@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).