public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] firewire: minor code refactoring for link internal data
Date: Tue, 30 Jul 2024 21:36:12 +0900	[thread overview]
Message-ID: <20240730123612.GA206389@workstation.local> (raw)
In-Reply-To: <20240729134631.127189-1-o-takashi@sakamocchi.jp>

On Mon, Jul 29, 2024 at 10:46:28PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> The current implementation of both core functions and 1394 OHCI driver has
> some points that need to be refactored regarding the handling of link-
> internal data.
> 
> This patchset is for the purpose.
> 
> Takashi Sakamoto (3):
>   firewire: ohci: use TCODE_LINK_INTERNAL consistently
>   firewire: ohci: minor code refactoring to localize text table
>   firewire: core: use common helper function to serialize phy
>     configuration packet
> 
>  drivers/firewire/core-cdev.c        |  4 +++-
>  drivers/firewire/core-transaction.c |  2 +-
>  drivers/firewire/ohci.c             | 37 +++++++++++++++++------------
>  drivers/firewire/ohci.h             |  1 -
>  4 files changed, 26 insertions(+), 18 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2024-07-30 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 13:46 [PATCH 0/3] firewire: minor code refactoring for link internal data Takashi Sakamoto
2024-07-29 13:46 ` [PATCH 1/3] firewire: ohci: use TCODE_LINK_INTERNAL consistently Takashi Sakamoto
2024-07-29 13:46 ` [PATCH 2/3] firewire: ohci: minor code refactoring to localize text table Takashi Sakamoto
2024-07-29 13:46 ` [PATCH 3/3] firewire: core: use common helper function to serialize phy configuration packet Takashi Sakamoto
2024-07-30 12:36 ` Takashi Sakamoto [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=20240730123612.GA206389@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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