From: Peter Korsgaard <peter@korsgaard.com>
To: Mohammed Billoo <mab@mab-labs.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: ocores: add gaisler to platform data
Date: Thu, 13 Aug 2020 18:29:02 +0200 [thread overview]
Message-ID: <87h7t67bn5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CALkjhPrz=0q+sKsB9Y=i4LCCuFVg-bGSzGDyAHaE-XE=qBrVXQ@mail.gmail.com> (Mohammed Billoo's message of "Thu, 13 Aug 2020 10:49:59 -0400")
>>>>> "Mohammed" == Mohammed Billoo <mab@mab-labs.com> writes:
Hi,
> And the answer is a patch series (I couldn't figure out the appropriate
> term to google).
Indeed. Please send a patch series for the needed changes to linux-i2c
and put me in CC.
> Also, it looks like the linux-i2c mailing list no longer exists?
It does. Perhaps you need to subscribe to be able to post? My earlier
reply did make it to the list:
https://marc.info/?l=linux-i2c&m=159732786421840&w=2
> On Thu, Aug 13, 2020 at 10:33 AM Mohammed Billoo <mab@mab-labs.com> wrote:
>> Peter,
>>
>> Thanks for your comment. Would you like me to resubmit the patch with your
>> suggestions?
>>
>> Also, we'll need to incorporate big/little-endian with the GRLIB accessors
>> as well (I ran into an issue where a vendor-specific AHB bridge had
>> endianness conversion, but the IP designer didn't realize that and so I
>> needed an accessor for both GRLIB and big-endian). I'm not sure what the
>> best-practice for multiple patches is. Should I submit patch N assuming
>> patch N-1 was applied?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-08-13 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200811134426.7613-1-mab@mab-labs.com>
2020-08-13 14:10 ` [PATCH] i2c: ocores: add gaisler to platform data Peter Korsgaard
[not found] ` <CALkjhPpF9wqaZGWQSZ9FphtcXD_obYubFX4te9xtcDdOP4M_gg@mail.gmail.com>
[not found] ` <CALkjhPrz=0q+sKsB9Y=i4LCCuFVg-bGSzGDyAHaE-XE=qBrVXQ@mail.gmail.com>
2020-08-13 16:29 ` Peter Korsgaard [this message]
2020-08-13 18:42 ` 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=87h7t67bn5.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mab@mab-labs.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