On Thursday, November 19, 2015 at 01:05:15 PM, Ulf Hansson wrote: > On 19 November 2015 at 12:58, Marek Vasut <marex@xxxxxxx> wrote: > > On Thursday, November 19, 2015 at 12:52:06 PM, Ulf Hansson wrote: > >> On 18 November 2015 at 10:47, Marek Vasut <marex@xxxxxxx> wrote: > >> > This is a trivial patch which fixes printed strings split across two > >> > or more lines in the source. I tried to grep for some error output*, > >> > but I couldn't find it easily because it was broken across multiple > >> > lines. This patch makes my life easier. > >> > > >> > * in particular "Timeout waiting for hardware interrupt." > >> > > >> > Signed-off-by: Marek Vasut <marex@xxxxxxx> > >> > Cc: Ulf Hansson <ulf.hansson@xxxxxxxxxx> > > > > Hi! > > > >> Future wise, no need to add a Cc tag here. You should send the patch > >> to me anyway. > > > > Are CC tags now frowned upon? In case I have multiple distinct patches > > (which go to distinct lists/recipients) in a queue, I use these CC tags > > to track who to keep in a loop. Is there some better way to do this? > > As this was a separate patch I didn't quite understand the Cc. > If the patch is a part of a patchset, it makes more sense if it > involves different subsystems/maintainers. It does, but the patches are orthogonal in my case, so I am sending them using git send-email -1 or such. > Anyway, no big deal for me! If I don't like the Cc tag, I can easily > remove it when applying. Thanks :-) Best regards, Marek Vasut -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
