linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Geyslan G. Bem" <geyslan@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Peter Senna Tschudin <peter.senna@gmail.com>,
	linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] usb: whci: replace dma_pool_alloc and memset with dma_pool_zalloc
Date: Fri, 4 Dec 2015 15:05:38 -0300	[thread overview]
Message-ID: <CAGG-pUQXtJx97vB3OLsaLoC1n_Hx0JGTq9_e+BcATvxCw2DjMg@mail.gmail.com> (raw)
In-Reply-To: <20151204171813.GB19351@kroah.com>

2015-12-04 14:18 GMT-03:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> On Fri, Dec 04, 2015 at 02:13:35PM -0300, Geyslan G. Bem wrote:
>> 2015-12-04 13:44 GMT-03:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
>> > On Fri, Dec 04, 2015 at 01:33:18PM -0300, Geyslan G. Bem wrote:
>> >>
>> >> If you wish, you could list me subsystems in need of maintenance.
>> >
>> > I don't understand what you mean by this.
>>
>> I meant that would be great to know which usb subsystems you do prefer
>> that I continue cleaning/refactoring or if any would be ok. :)
>
> Any part of the drivers/usb/* tree that you find needs cleanups and
> fixes like these are great to do, please send patches for this, I'll
> gladly take them.

Nice, I'll indeed.

Thanks.
>
> thanks,
>
> gre k-h



-- 
Regards,

Geyslan G. Bem
hackingbits.com

      reply	other threads:[~2015-12-04 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 20:43 [PATCH 2/3] usb: whci: replace dma_pool_alloc and memset with dma_pool_zalloc Geyslan G. Bem
2015-12-04 16:25 ` Greg Kroah-Hartman
2015-12-04 16:33   ` Geyslan G. Bem
2015-12-04 16:44     ` Greg Kroah-Hartman
2015-12-04 17:13       ` Geyslan G. Bem
2015-12-04 17:18         ` Greg Kroah-Hartman
2015-12-04 18:05           ` Geyslan G. Bem [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=CAGG-pUQXtJx97vB3OLsaLoC1n_Hx0JGTq9_e+BcATvxCw2DjMg@mail.gmail.com \
    --to=geyslan@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.senna@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).