All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/4] drivers: musb-new: remove writes{bwlq} and reads{bwlq}.
Date: Wed, 16 Mar 2016 16:44:20 +0100	[thread overview]
Message-ID: <56E97F54.7040209@denx.de> (raw)
In-Reply-To: <56E8FF05.4090901@microchip.com>

On 03/16/2016 07:36 AM, Purna Chandra Mandal wrote:
> On 03/15/2016 11:40 PM, Marek Vasut wrote:
> 
>> On 03/15/2016 01:44 PM, Purna Chandra Mandal wrote:
>>> Moved definition of writes{bwlq} and reads{bwlq} into arch.
>>> There is no need of having arch specific wrapper in driver.
>> And so the patch does ... what exactly ? I cannot figure it out just by
>> reading the commit message, sorry.
>>
>> The patch itself is fine of course, but please fix the commit message.
> 
> I hope new commit message will do.
> "Definition of writes{bwlq}, reads{bwlq} are now added into arch specific asm/io.h.
>  So removing them from driver to fix re-definition error.
> "

Yes please :)

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-03-16 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 12:44 [U-Boot] [PATCH v3 1/4] arm: add missing writes{bwql}, reads{bwql} Purna Chandra Mandal
2016-03-15 12:44 ` [U-Boot] [PATCH v3 2/4] drivers: musb-new: remove writes{bwlq} and reads{bwlq} Purna Chandra Mandal
2016-03-15 18:10   ` Marek Vasut
2016-03-16  6:36     ` Purna Chandra Mandal
2016-03-16 15:44       ` Marek Vasut [this message]
2016-03-15 12:44 ` [U-Boot] [PATCH v3 3/4] drivers: musb-new: Add USB DRC driver for Microchip PIC32 OTG controller Purna Chandra Mandal
2016-03-15 18:19   ` Marek Vasut
2016-03-16  9:58     ` Purna Chandra Mandal
2016-03-16 15:48       ` Marek Vasut
2016-03-17  9:58         ` Purna Chandra Mandal
2016-03-17 11:31           ` Marek Vasut
2016-03-15 12:44 ` [U-Boot] [PATCH v3 4/4] board: pic32mzda: enable USB-host, USB-storage support Purna Chandra Mandal
2016-03-16  9:12   ` Daniel Schwierzeck
2016-03-16 15:49     ` Marek Vasut

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=56E97F54.7040209@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.