All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartley Sweeten <HartleyS@visionengravers.com>
To: Chase Southwood <chase.southwood@yahoo.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 2/2 v3] staging: comedi: addi_apci_1564: fixup and absorb apci1564_reset()
Date: Thu, 17 Apr 2014 00:04:36 +0000	[thread overview]
Message-ID: <DC148C5AA1CEBA4E87973D432B1C2D8825E051E5@P3PWEX4MB008.ex4.secureserver.net> (raw)
In-Reply-To: <1397692382.80906.YahooMailNeo@web164005.mail.gq1.yahoo.com>

On Wednesday, April 16, 2014 4:53 PM, Chase Southwood wrote:
>>On Wednesday, April 16, 2014 6:36 PM, Hartley Sweeten <HartleyS@visionengravers.com> wrote:
>>>On Wednesday, April 16, 2014 4:34 PM, Chase Southwood wrote:
>>>Move apci1564_reset() from hwdrv_apci1564.c to addi_apci_1564.c.  The
>>>function was very messy and failed to reset a couple registers, these
>>>issues were fixed on the move.>
>>
>>The commit message needs updated. You are no longer moving the function.
>>
>
> Erm...in the PATCH v3 I just sent, it has been moved as described here, so at least for
> what is happening now, this changelog is accurate.  Would you like me to no longer move
> the function for the time being?

Ah, missed that you moved it before the struct addi_board definition.

Hmmm... I think it would be cleaner if you moved the function after separating
this driver from the addi_common.c file. Then the moved functions can be put
into the driver in "cleaner" locations and avoid any forward declaration junk.

The brute force way to do this is just copy the contents of addi_common.c to
the driver and remove the #include. Then you can move the functions from
the hwrdv_apci1564.c file to the driver, and remove them from the boardinfo,
as needed.

Once you get the addi_common.c stuff localized you should fine that much
of it is just NOP code for this driver. Those pieces then just need to be ripped
out.

Have fun...

Hartley


      parent reply	other threads:[~2014-04-17  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1397691269-24940-1-git-send-email-chase.southwood@yahoo.com>
2014-04-16 23:36 ` [PATCH 2/2 v3] staging: comedi: addi_apci_1564: fixup and absorb apci1564_reset() Hartley Sweeten
     [not found]   ` <1397692382.80906.YahooMailNeo@web164005.mail.gq1.yahoo.com>
2014-04-17  0:04     ` Hartley Sweeten [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=DC148C5AA1CEBA4E87973D432B1C2D8825E051E5@P3PWEX4MB008.ex4.secureserver.net \
    --to=hartleys@visionengravers.com \
    --cc=abbotti@mev.co.uk \
    --cc=chase.southwood@yahoo.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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 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.