devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Ricardo Ribalda Delgado
	<ricardo.ribalda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: Fwd: [PATCH] x86/devicetree: Fix compile warnings on AMD64
Date: Thu, 28 Aug 2014 15:34:34 +0200	[thread overview]
Message-ID: <53FF2FEA.8070302@linutronix.de> (raw)
In-Reply-To: <CAPybu_2shGr+OROg=QkQwmXW4wmNEVzKypKOJRyiZxZh37bp3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 08/28/2014 03:23 PM, Ricardo Ribalda Delgado wrote:
> The problem is that it is a fwd message?  I did send it first the 5th
Yes.

> of August and did not get any feedback, this is why I tried to
> different destinations. Shall I just resend it?

Usually you just add a RESEND / REPOST before the patch tag. The
forward header makes the submission useless (unless the TIP team has
time to manually edit the patch).

> I am working on an fpga camera (http://qtec.com) connected via pcie to
> an amd fusion APU (64 bits). The hardware of the fpga is described
> with devicetrees.

So you are telling me that there is (or will be) 64bit x86 hardware
which is using the device tree instead EFI, SFI or something like that.
Is that so?
If so it is worth mentioning that in the patch description that this
code is used on x86 hard which is not yet part of the kernel.
Either way, the x86 team + lkml is the destination that should apply
that patch so a proper repost (with the altered description I
mentioned) would be nice.

> Thanks!

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-08-28 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1407230388-14211-1-git-send-email-ricardo.ribalda@gmail.com>
     [not found] ` <1407230388-14211-1-git-send-email-ricardo.ribalda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-28 13:04   ` Fwd: [PATCH] x86/devicetree: Fix compile warnings on AMD64 Ricardo Ribalda Delgado
     [not found]     ` <CAPybu_39pLQ6gvKOPuLNCnn46Y50QU36C5thJmxrNmCzGN+MAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-28 13:13       ` Sebastian Andrzej Siewior
     [not found]         ` <53FF2B17.4030600-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2014-08-28 13:23           ` Ricardo Ribalda Delgado
     [not found]             ` <CAPybu_2shGr+OROg=QkQwmXW4wmNEVzKypKOJRyiZxZh37bp3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-28 13:34               ` Sebastian Andrzej Siewior [this message]

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=53FF2FEA.8070302@linutronix.de \
    --to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=ricardo.ribalda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).