linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: boris.brezillon@bootlin.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] clk: at91: Added more information logging
Date: Tue, 10 Apr 2018 10:12:02 +0200	[thread overview]
Message-ID: <20180410101202.2abdf68f@bbrezillon> (raw)
In-Reply-To: <20180410001551.GA62208@hak8or>

Hi Marcin

On Mon, 9 Apr 2018 20:15:51 -0400
Marcin Ziemianowicz <marcin@ziemianowicz.com> wrote:

> This is a series of patches which resolves set_rate() for the PLL not
> having any effect and therefore the USB Host port not working. Also, a
> few messages were added which may be helpful in the future when others
> are working with USB clocking.

Can you please send patch series in a threaded manner (the cover
letter being the mail email and patches 1 to X being tagged as
'In-reply-to')? Normally, git send-email takes care of that for you if
you do

# git send-email *.patch

> 
> Changes since V1:
>   Added patch set cover letter
>   Shortened lines which were over >80 characters long
>   > Comment by Greg Kroah-Hartman about "from" field in email addressed
>   > Comment by Alan Stern about redundant debug lines addressed  
> 
> hak8or (2):
>   clk: at91: Added more information logging.
>   clk: at91: Fix for PLL set_rate changes not being actually written to
>     PLL peripheral bits
> 
>  drivers/clk/at91/clk-pll.c   | 14 +++++++++++++-
>  drivers/clk/at91/clk-usb.c   | 10 ++++++++--
>  drivers/usb/host/ohci-at91.c | 16 ++++++++++------
>  3 files changed, 31 insertions(+), 9 deletions(-)
> 

      reply	other threads:[~2018-04-10  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  0:15 [PATCH v2 0/2] clk: at91: Added more information logging Marcin Ziemianowicz
2018-04-10  8:12 ` Boris Brezillon [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=20180410101202.2abdf68f@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).