From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] toshiba_acpi: Clean file plus some function renames
Date: Wed, 11 Feb 2015 21:30:37 -0800 [thread overview]
Message-ID: <20150212053037.GC30527@fury.dvhart.com> (raw)
In-Reply-To: <1423637040-6813-1-git-send-email-coproscefalo@gmail.com>
On Tue, Feb 10, 2015 at 11:43:55PM -0700, Azael Avalos wrote:
> These patches are simply "cleaning" the file, making it more readable
> and in the process, make it comply according to coding style.
>
> --->8---
> Darren,
>
> I'm sending these patches now and let you decide if you want them for
> 3.20 as the merge window is still open or queue them up for 3.21 :-)
Queued, thanks.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2015-02-12 5:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 6:43 [PATCH 0/5] toshiba_acpi: Clean file plus some function renames Azael Avalos
2015-02-11 6:43 ` [PATCH 1/5] toshiba_acpi: Clean file according to coding style Azael Avalos
2015-02-11 6:43 ` [PATCH 2/5] Documentation/ABI: Add file describing the sysfs entries for toshiba_acpi Azael Avalos
[not found] ` <1423637040-6813-3-git-send-email-coproscefalo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-12 5:38 ` Darren Hart
[not found] ` <20150212053807.GD30527-JIrPihikzLEQaXB9iyTzyw@public.gmane.org>
2015-02-12 5:42 ` Azael Avalos
2015-02-11 6:43 ` [PATCH 3/5] toshiba_acpi: Move sysfs function and struct declarations further down Azael Avalos
2015-02-11 6:43 ` [PATCH 4/5] toshiba_acpi: Drop the toshiba_ prefix from sysfs function names Azael Avalos
2015-02-11 6:44 ` [PATCH 5/5] toshiba_acpi: Make use of DEVICE_ATTR_{RO, RW} macros Azael Avalos
2015-02-12 5:30 ` Darren Hart [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=20150212053037.GC30527@fury.dvhart.com \
--to=dvhart@infradead.org \
--cc=coproscefalo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).