From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/4] Unify PCI clock detection in the HPT37x/HPT3x2N drivers
Date: Wed, 8 Jun 2022 15:47:24 +0900 [thread overview]
Message-ID: <b7ca6700-1896-ec12-d298-c2341c79f169@opensource.wdc.com> (raw)
In-Reply-To: <20220515204126.4866-1-s.shtylyov@omp.ru>
On 5/16/22 05:41, Sergey Shtylyov wrote:
> Here are 4 patches against the 'for-next' branch of Damien Le Moal's
> 'libata.git' repo.
> The PCI clock frequency detection code in the HighPoint HPT37x/HPT3x2N drivers
> has needlessly diverged, so trying to unify it...
>
> Sergey Shtylyov (4):
> ata: pata_hpt37x: move claculating PCI clock from hpt37x_clock_slot()
> ata: pata_hpt37x: factor out hpt37x_pci_clock()
> ata: pata_hpt37x: merge hpt374_read_freq() to hpt37x_pci_clock()
> ata: pata_hpt3x2n: pass base DPLL frequency to hpt3x2n_pci_clock()
>
> drivers/ata/pata_hpt37x.c | 113 +++++++++++++++++++------------------
> drivers/ata/pata_hpt3x2n.c | 19 ++++---
> 2 files changed, 70 insertions(+), 62 deletions(-)
>
Applied to for-5.20. Thanks !
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-06-08 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 20:41 [PATCH 0/4] Unify PCI clock detection in the HPT37x/HPT3x2N drivers Sergey Shtylyov
2022-05-15 20:41 ` [PATCH 1/4] ata: pata_hpt37x: move claculating PCI clock from hpt37x_clock_slot() Sergey Shtylyov
2022-05-15 20:41 ` [PATCH 2/4] ata: pata_hpt37x: factor out hpt37x_pci_clock() Sergey Shtylyov
2022-05-15 20:41 ` [PATCH 3/4] ata: pata_hpt37x: merge hpt374_read_freq() to hpt37x_pci_clock() Sergey Shtylyov
2022-05-15 20:41 ` [PATCH 4/4] ata: pata_hpt3x2n: pass base DPLL frequency to hpt3x2n_pci_clock() Sergey Shtylyov
2022-06-08 6:47 ` Damien Le Moal [this message]
2022-06-08 17:15 ` [PATCH 0/4] Unify PCI clock detection in the HPT37x/HPT3x2N drivers Sergey Shtylyov
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=b7ca6700-1896-ec12-d298-c2341c79f169@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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