linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@kudzu.us>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	trivial@kernel.org, linux-renesas-soc@vger.kernel.org,
	Dave Jiang <dave.jiang@intel.com>,
	Allen Hubbe <Allen.Hubbe@emc.com>,
	linux-ntb@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] NTB: ntb_hw_idt: fix typo 'can by' to 'can be'
Date: Mon, 21 May 2018 20:35:31 -0400	[thread overview]
Message-ID: <20180522003531.GB3255@kudzu.us> (raw)
In-Reply-To: <20180511131236.GA24717@mobilestation>

On Fri, May 11, 2018 at 04:12:36PM +0300, Serge Semin wrote:
> On Sun, May 06, 2018 at 01:23:50PM +0200, Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > ---
> >  drivers/ntb/hw/idt/ntb_hw_idt.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/ntb/hw/idt/ntb_hw_idt.c b/drivers/ntb/hw/idt/ntb_hw_idt.c
> > index 8d98872d0983b7..dbe72f116017ab 100644
> > --- a/drivers/ntb/hw/idt/ntb_hw_idt.c
> > +++ b/drivers/ntb/hw/idt/ntb_hw_idt.c
> > @@ -1401,7 +1401,7 @@ static int idt_ntb_peer_mw_clear_trans(struct ntb_dev *ntb, int pidx,
> >   *                          5. Doorbell operations
> >   *
> >   *    Doorbell functionality of IDT PCIe-switches is pretty unusual. First of
> > - * all there is global doorbell register which state can by changed by any
> > + * all there is global doorbell register which state can be changed by any
> >   * NT-function of the IDT device in accordance with global permissions. These
> >   * permissions configs are not supported by NTB API, so it must be done by
> >   * either BIOS or EEPROM settings. In the same way the state of the global
> 
> Acked-by: Serge Semin <fancer.lancer@gmail.com>

Applied to my ntb-next branch.

Thanks,
Jon


> 
> > -- 
> > 2.11.0
> > 

  reply	other threads:[~2018-05-22  0:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 11:23 [PATCH 0/9] tree-wide: fix typo 'can by' to 'can be' Wolfram Sang
2018-05-06 11:23 ` [PATCH 1/9] dt-bindings: i2c: " Wolfram Sang
2018-05-10 10:41   ` Wolfram Sang
2018-05-06 11:23 ` [PATCH 2/9] powerpc/watchdog: " Wolfram Sang
2018-05-10 14:06   ` [2/9] " Michael Ellerman
2018-05-06 11:23 ` [PATCH 3/9] base: core: " Wolfram Sang
2018-05-06 11:23 ` [PATCH 4/9] hwmon: fschmd: " Wolfram Sang
2018-05-08  4:42   ` Guenter Roeck
2018-05-06 11:23 ` [PATCH 5/9] input: ati_remote2: " Wolfram Sang
2018-05-08 22:39   ` Dmitry Torokhov
2018-05-06 11:23 ` [PATCH 6/9] NTB: ntb_hw_idt: " Wolfram Sang
2018-05-11 13:12   ` Serge Semin
2018-05-22  0:35     ` Jon Mason [this message]
2018-05-06 11:23 ` [PATCH 7/9] reiserfs: journal: " Wolfram Sang
2018-05-06 11:23 ` [PATCH 8/9] net: flow_dissector: " Wolfram Sang
2018-05-08  3:47   ` David Miller
2018-05-06 11:23 ` [PATCH 9/9] objtool: " Wolfram Sang

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=20180522003531.GB3255@kudzu.us \
    --to=jdmason@kudzu.us \
    --cc=Allen.Hubbe@emc.com \
    --cc=dave.jiang@intel.com \
    --cc=fancer.lancer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntb@googlegroups.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=trivial@kernel.org \
    --cc=wsa+renesas@sang-engineering.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).