From: Tom Rini <trini@konsulko.com>
To: Stefan Roese <sr@denx.de>
Cc: "Pali Rohár" <pali@kernel.org>,
"Adrian Fiergolski" <adrian.fiergolski@fastree3d.com>,
"Marek Behún" <marek.behun@nic.cz>, "Wolfgang Denk" <wd@denx.de>,
"Simon Glass" <sjg@chromium.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH] misc: atsha204a: Fix big endian support
Date: Thu, 7 Apr 2022 09:47:09 -0400 [thread overview]
Message-ID: <20220407134709.GP14282@bill-the-cat> (raw)
In-Reply-To: <5586aa6e-c935-6a7b-1401-c42640282681@denx.de>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Thu, Apr 07, 2022 at 03:31:25PM +0200, Stefan Roese wrote:
> Added Tom to To...
>
> On 4/7/22 10:29, Pali Rohár wrote:
> > On Monday 04 April 2022 09:43:21 Stefan Roese wrote:
> > > On 4/3/22 00:36, Pali Rohár wrote:
> > > > Callers of function atsha204a_crc16() expect to return value in host cpu
> > > > endianity. So remove cpu_to_le16() conversion.
> > > >
> > > > Signed-off-by: Pali Rohár <pali@kernel.org>
> > >
> > > Reviewed-by: Stefan Roese <sr@denx.de>
> >
> > Hello Stefan! Would you or somebody else take this patch?
> >
> > Because I have some other u-boot generic patches which touches this
> > driver and I'm waiting until this simple change would be merged first.
>
> In general I could do this. But I'm leaving for a vacation in a few days
> and I'm not sure, if I can squeeze enough "free time" to handle my
> "U-Boot work".
>
> Tom, could you please pull this patch directly?
OK, I'll assign it to myself in patchwork.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-04-07 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 22:36 [PATCH] misc: atsha204a: Fix big endian support Pali Rohár
2022-04-04 7:43 ` Stefan Roese
2022-04-07 8:29 ` Pali Rohár
2022-04-07 13:31 ` Stefan Roese
2022-04-07 13:47 ` Tom Rini [this message]
2022-04-12 9:37 ` Pali Rohár
2022-04-04 7:57 ` Marek Behún
2022-04-15 12:07 ` Tom Rini
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=20220407134709.GP14282@bill-the-cat \
--to=trini@konsulko.com \
--cc=adrian.fiergolski@fastree3d.com \
--cc=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
/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