All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Ross Burton <ross.burton@arm.com>
Cc: "Purdie, Richard" <richard.purdie@linuxfoundation.org>,
	"otavio@ossystems.com.br" <otavio@ossystems.com.br>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] libusb1: Link with -latomic only if no atomic builtins
Date: Wed, 27 Jul 2022 12:45:33 -0400	[thread overview]
Message-ID: <fb3e160b-4c49-f08a-716d-1ed69ecb3c00@gmail.com> (raw)
In-Reply-To: <CAP9ODKpo9=JeKvdEK+kX5_2gVWv4haSyU1jYgFLGcwPci8qMsQ@mail.gmail.com>



On 7/27/22 12:41 PM, Otavio Salvador wrote:
> 
> 
> Em qua., 27 de jul. de 2022 às 13:35, Ross Burton <ross.burton@arm.com 
> <mailto:ross.burton@arm.com>> escreveu:
> 
>     Whoever adds the patch needs to add their S-o-b.
> 
> 
> The patch sanity check should warn about it as it does for the status 
> header. I said, RP can add it.

RP can do, but he can only do so much :) lets try to help him.
Its not something that can be added during applying patch which could be 
done, this needs to change the libusb1 patch and then final patch 
regenerated, its better if it can be done by you and resend a v2.

> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br <http://www.ossystems.com.br> 
> http://code.ossystems.com.br <http://code.ossystems.com.br>
> Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750
> 
> 
> 
> 

  reply	other threads:[~2022-07-27 16:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 12:00 [PATCH] libusb1: Link with -latomic only if no atomic builtins Otavio Salvador
2022-07-27 15:28 ` [OE-core] " Ross Burton
2022-07-27 16:20   ` Otavio Salvador
2022-07-27 16:35     ` Ross Burton
2022-07-27 16:41       ` Otavio Salvador
2022-07-27 16:45         ` Khem Raj [this message]
2022-07-27 16:55           ` Otavio Salvador
2022-07-27 17:56             ` Alexander Kanavin
2022-07-27 18:43         ` Ross Burton

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=fb3e160b-4c49-f08a-716d-1ed69ecb3c00@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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 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.