From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Frederich <jfrederich@gmail.com>
Cc: devel@driverdev.osuosl.org,
Jon Nettleton <jon.nettleton@gmail.com>,
Daniel Drake <dsd@laptop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: olpc_dcon: more big endian conformity
Date: Thu, 15 Aug 2013 17:22:04 -0700 [thread overview]
Message-ID: <20130816002204.GA16114@kroah.com> (raw)
In-Reply-To: <CAF92urqkWhXO0_DiFG5hp4qDXLYEoATrrvOw-JXQvWvHQp3QDQ@mail.gmail.com>
On Thu, Aug 15, 2013 at 09:54:05PM +0200, Jens Frederich wrote:
> On Mon, Aug 12, 2013 at 11:07 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Sun, Aug 04, 2013 at 11:04:16PM +0200, Jens Frederich wrote:
> >> Using an int which is casted to unsigned char as inbuf is messy.
> >> The code won't work on big endian systems. The patch should fix
> >> this.
> >>
> >> Signed-off-by: Jens Frederich <jfrederich@gmail.com>
> >
> > This patch doesn't apply at all, can you refresh it against my
> > staging-next branch and resend it so that I can apply it?
> >
>
> Sorry for the duplicated patch 3. The subject:
> [PATCH] Staging: olpc_dcon: more big endian conformity and
> [PATCH 3/3] Staging: olpc_dcon: more big endian conformity
> is equal for the Google mail client and lands in the same
> thread. I'd use Mutt.
I do use mutt, and see two copies of this patch sent.
What happened to patch 1/3, I never got that.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-16 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 21:04 [PATCH] Staging: olpc_dcon: more big endian conformity Jens Frederich
2013-08-12 21:07 ` Greg KH
2013-08-15 19:18 ` Jens Frederich
2013-08-15 19:54 ` Jens Frederich
2013-08-16 0:22 ` Greg KH [this message]
2013-08-16 5:58 ` Jens Frederich
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=20130816002204.GA16114@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dsd@laptop.org \
--cc=jfrederich@gmail.com \
--cc=jon.nettleton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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