All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Daniel Axtens <dja@axtens.net>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@ozlabs.org, benh@kernel.crashing.org,
	imunsie@au.ibm.com
Subject: Re: [PATCH] cxl: Don't ignore add_process_element result when attaching context
Date: Wed, 05 Aug 2015 17:59:21 +1000	[thread overview]
Message-ID: <1438761561.20978.3.camel@neuling.org> (raw)
In-Reply-To: <1438144834.28422.46.camel@axtens.net>

On Wed, 2015-07-29 at 14:40 +1000, Daniel Axtens wrote:
> On Wed, 2015-07-29 at 14:25 +1000, Michael Ellerman wrote:
> > On Wed, 2015-07-29 at 14:07 +1000, Daniel Axtens wrote:
> > > Previously, when attaching a context in dedicated mode, we ignored
> >=20
> > Previously? You mean currently? Now is before this patch is applied.
> I do mean currently. Apologies for the temporal confusion :)
>=20
> >=20
> > > the result of add_process_element, which could potentially fail.
> > >=20
> > > If add_process_element returns and error, pass it back to the caller.
> >                                    ^
> >=20
> > I can fix.
> >=20
> Many thanks: it's good to know that my spelling mistakes will only be
> immortalised in the list archives rather than in the kernel's git
> history. :p

Not to mention the double negative in the patch subject! "Don't
ignore"... come on!?!?  :-P

Mikey

  reply	other threads:[~2015-08-05  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  4:07 [PATCH] cxl: Don't ignore add_process_element result when attaching context Daniel Axtens
2015-07-29  4:25 ` Michael Ellerman
2015-07-29  4:40   ` Daniel Axtens
2015-08-05  7:59     ` Michael Neuling [this message]
2015-08-10  9:27 ` Michael Ellerman

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=1438761561.20978.3.camel@neuling.org \
    --to=mikey@neuling.org \
    --cc=benh@kernel.crashing.org \
    --cc=dja@axtens.net \
    --cc=imunsie@au.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.