linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Kalle Valo" <kvalo@adurom.com>,
	"Nathan Hintz" <nlhintz@hotmail.com>,
	linux-wireless@vger.kernel.org, hauke@hauke-m.de
Subject: Re: [PATCH v2 0/6] BCMA Cumulative patches from OpenWRT
Date: Wed, 2 May 2012 20:53:28 +0200	[thread overview]
Message-ID: <4FA182A8.8080604@broadcom.com> (raw)
In-Reply-To: <20120502181157.GC9285@tuxdriver.com>

On 05/02/2012 08:11 PM, John W. Linville wrote:
> On Thu, Apr 26, 2012 at 02:50:54PM +0300, Kalle Valo wrote:
>> "Arend van Spriel" <arend@broadcom.com> writes:
>>
>>> On 04/26/2012 06:23 AM, Nathan Hintz wrote:
>>>> Nathan Hintz (6):
>>>>    bcma: Find names of non BCM cores
>>>>    bcma: Move initialization of SPROM to prevent overwrite
>>>>    bcma: Account for variable PCI memory base/size
>>>>    bcma: reads/writes are always 4 bytes, so always map 4 bytes
>>>>    bcma: Add __devexit to bcma_host_pci_remove
>>>>    bcma: Add flush for BCMA_RESET_CTL write
>>>>
>>>>   arch/mips/bcm47xx/setup.c      |    4 +++
>>>>   arch/mips/bcm47xx/sprom.c      |    2 -
>>>>   drivers/bcma/core.c            |    1 +
>>>>   drivers/bcma/driver_pci_host.c |   10 +++---
>>>>   drivers/bcma/host_pci.c        |    4 +-
>>>>   drivers/bcma/scan.c            |   54 +++++++++++++++++++++++++++++----------
>>>>   6 files changed, 52 insertions(+), 23 deletions(-)
>>>>
>>>
>>> None of these patches have any description. Some motivation for the
>>> changes would be appreciated like 'reported problem', 'new target
>>> support', etc.
>>
>> I would say that it's required. Anyone can see the diff and see what was
>> changed, but nobody will figure out why the change was made unless it's
>> described in the commit log. So it's important to answer the question
>> "Why?".
> 
> Will we be seeing this patchset reposted with better changelogs?
> 
> John

Although not strongly stated by me I was certainly expecting a re-post.

Gr. AvS


  reply	other threads:[~2012-05-02 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  4:23 [PATCH v2 0/6] BCMA Cumulative patches from OpenWRT Nathan Hintz
2012-04-26  8:56 ` Arend van Spriel
2012-04-26 11:50   ` Kalle Valo
2012-05-02 18:11     ` John W. Linville
2012-05-02 18:53       ` Arend van Spriel [this message]
2012-05-03  5:04         ` Nathan Hintz
2012-05-03  6:11           ` Arend van Spriel

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=4FA182A8.8080604@broadcom.com \
    --to=arend@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=kvalo@adurom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nlhintz@hotmail.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).